
execute CreateSettingGroup('Scan Screens', 'N', '');
execute CreateSettingGroup('General', 'N', '');
execute CreateSettingGroup('Wearer Screen Settings', 'N', '');
execute CreateSettingGroup('Linen Recording', 'N', '');
execute CreateSettingGroup('Stockroom', 'N', '');
execute CreateSettingGroup('ABS', 'Y', 'IVAN');
execute CreateSettingGroup('Billing', 'N', '');
execute CreateSettingGroup('Customer Screen Settings', 'N', '');
execute CreateSettingGroup('Product Screen Settings', 'N', '');
execute CreateSettingGroup('Product List / Cust. Settings', 'N', '');
execute CreateSettingGroup('Delivery Note', 'N', '');
execute CreateSettingGroup('Financial Export', 'N', '');
execute CreateSettingGroup('Garment Recording', 'N', '');
execute CreateSettingGroup('File Locations', 'N', '');
execute CreateSettingGroup('E-Mail settings', 'N', '');
execute CreateSettingGroup('WebApplication', 'N', '');
execute CreateSettingGroup('Residential Services', 'N', '');
execute CreateSettingGroup('BNL specific settings', 'N', '');
execute CreateSettingGroup('Route Assistant PDA', 'N', '');
execute CreateSettingGroup('Security', 'N', '');
execute CreateSettingGroup('Washroom Services', 'N', '');
execute CreateSettingGroup('ORS', 'N', '');
execute CreateSettingGroup('App Settings', 'N', '');
execute CreateSettingGroup('Picking Assistant PDA', 'N', '');
execute CreateSettingGroup('Linen Assistant PDA', 'N', '');
execute CreateSettingGroup('Garment Assistant App', 'N', '');
execute CreateSystemSetting('Scan Screens', 'ALLOWREPAIRSCAN', '1', 'I', '1', 'N', 'N', 1, 4, '', 'Defined which garments may be repaired:'|| chr(10) ||'1 = All garments                                                                       '|| chr(10) ||'2 = Only when charged for the customer'|| chr(10) ||'3 = Only for laundry owned items'|| chr(10) ||'4 = Only when charged and laundry owned'|| chr(10) ||'This setting is also used in interface with sorting systems.', 'Y');
execute CreateSystemSetting('Scan Screens', 'AUTOASSIGNUNKNOWNTAGPRC', '60', 'I', '60', 'N', 'N', 0, 100, '', 'Unknown UHF tagnumbers scanned during stack check or bundle assembly can automatically be inserted in the database and assigned to the same product and size as the other items in that stack or bundle.'|| chr(10) ||'This setting defines the minimum percentage of assigned items that need to be in the stack.'|| chr(10) ||'For example with this setting set to 60% then a stack/bundle of 5 pieces must have at least 3 assigned items and 2 may be unassigned. '|| chr(10) ||'Only works for pool items. '|| chr(10) ||'See also setting: AUTOASSIGNUNKNOWNTAGS.', 'N');
execute CreateSystemSetting('Scan Screens', 'AUTOASSIGNUNKNOWNTAGS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if UHF tagnumbers scanned during stack check or bundle assembly are automatically inserted in the database and assigned to the same product and size as the other items in that stack or bundle.'|| chr(10) ||'Only works for pool items. Auto assign only takes place when there is a minimum % of assigned items in the stack see setting: AUTOASSIGNUNKNOWNTAGPRC.', 'N');
execute CreateSystemSetting('Scan Screens', 'AUTOCREATEBUNDLETIMEOUT', '500', 'I', '500', 'N', 'N', 1, 1500, '', 'This setting defines the timeframe in milliseconds in which the multi-read antenna(s) can still scan additional ID codes after the requested number of items has already been scanned. After this interval has passed, automatically a unique bundle will be created (minimum timeout 1 millisecond, maximum 1,5 seconds).'|| chr(10) ||'This setting is only relevant when the module UNIQUEBUNDLESMULTIREAD is active and the system setting AUTOCREATEUNIQUEBUNDLE is set to 1.', 'N');
execute CreateSystemSetting('Scan Screens', 'AUTOCREATEUNIQUEBUNDLE', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'This setting defines whether a unique bundle should be created automatically when the number of scanned items matches the number of required items for this type of bundle. Or whether this is always a user decision and the user explicitly has to press the "Create Bundle" button to start the actual creation process.'|| chr(10) ||'0 = Bundle should be created manually'|| chr(10) ||'1 = Bundle should be created automatically'|| chr(10) ||'This setting is only relevant when the module UNIQUEBUNDLESMULTIREAD is active.', 'N');
execute CreateSystemSetting('Scan Screens', 'BATCHJOBINSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, it is allowed to select an existing batchjob instead of creating a new one. This setting is only used for the module BATCHJOB.', 'N');
execute CreateSystemSetting('Scan Screens', 'BRINGINCIRCATINSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, items that are scanned in with status Assigned will not be changed to status In Circulation. This can be used when items are issued via a central stockroom and send to the plant where they are washed first before they are delivered to the customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'BULKPUTUPEXTRASCANS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This system setting affects the multiread functionality from the Outscan bulk put up per route screen.'|| chr(10) ||''|| chr(10) ||'1 =  the Accept button is disabled when there are scans that do not belong to the current route or that are scanned too much (more scanned than needed). The user is forced to reject the scans in this situation.'|| chr(10) ||'0 = the Accept button is not affected. ', 'N');
execute CreateSystemSetting('Scan Screens', 'CHANGESCANDATE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting can be used to change the scandate (production date). For instance when because of a holiday a customer is scanned on a different date, it can be usefull to set the scandate to the original date because of route and outgoing date calculation. However the scans will still be registered on the systemdate, for production overviews.'|| chr(10) ||'0 = Scandate cannot be changed manually. The scandate is always the systemdate.'|| chr(10) ||'1 = Scandate can be changed using a button.'|| chr(10) ||'2 = Scandate can be changed using a button, at startup first the scandate must be selected.'|| chr(10) ||'Changing the scandate is only implemented for inscan.', 'N');
execute CreateSystemSetting('Scan Screens', 'CHECKCUSTOMERDELSCHEMEINS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1 if the first item is scanned in for a customer and this customer has multiple delivery days, a popup screen is opened that allows to adjust the scan date', 'N');
execute CreateSystemSetting('Scan Screens', 'CHECKPICKEDUPCONTAINERS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting check if for inscan date and soil count entry per consumption point date exists a pickedupcontainer. Possible values:'|| chr(10) ||'0 - no check for picked up container (default value)'|| chr(10) ||'1 - Check in pickedupcontainers that exists an active stop for customer and at least one container type for that distribution point', 'N');
execute CreateSystemSetting('Scan Screens', 'CHECKSPECIALSCANSDAYS', '7', 'I', '7', 'Y', 'N', 0, 99, '', 'Number of days the system will check for special scans. Only used in module special scans.', 'N');
execute CreateSystemSetting('Scan Screens', 'CHECKWOREPLACEMENT', '0', 'I', '0', 'Y', 'Y', 0, 1, '', '0 = before replacing an item from Outscan Sort Batch NO check is done on outstanding work orders for the current wearer and product (default)'|| chr(10) ||'1 = before replacing an item from Outscan Sort Batch a check is done on outstanding work orders for the current wearer and product; if found, the user can choose if he still wants to mark the item for replacement', 'N');
execute CreateSystemSetting('Scan Screens', 'COGADDWEARERALLOWED', 'Y', 'B', 'Y', 'N', 'N', null, null, 'Y;N', 'Allow to add a new wearer in add COG item screen (at inscan)', 'N');
execute CreateSystemSetting('Scan Screens', 'COGRULEREISSUEDRAGGEDITEM', '1', 'I', '1', 'N', 'N', 0, 1, '', 'This setting will be used to control whether it must be checked if a ragged item has been charged for residual value in case it is re-issued. Possible values:'|| chr(10) ||'0 = Do not take into account whether item has been charged for residual value upon re-issue'|| chr(10) ||'1 = Take into account whether item has been charged for residual value upon re-issue'|| chr(10) ||''|| chr(10) ||'When the item has been charged for residual value and it is re-issued then it is considered customer owned when the setting is set to 1. When set to 0, it will get the LOG/COG status at the moment it was ragged.', 'N');
execute CreateSystemSetting('Scan Screens', 'COGSELECTSIZEFM', 'N', 'B', 'N', 'N', 'N', null, null, 'Y;N', 'Allow to select size and finishing method in screen for adding COG items at inscan.'|| chr(10) ||'Used for optional module EXTENDEDCODEUNIQUECOG', 'N');
execute CreateSystemSetting('Scan Screens', 'CONFIRMASSIGNMULTIREAD', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'For issue screens this setting allows you to overrule the workstation setting to for confirming or rejecting multiread scans.'|| chr(10) ||'When this setting is set to Y the confirm and reject buttons in multiread issue screens are enabled always.'|| chr(10) ||'When this it is set to N the confirm and reject buttons are only visible when defined so at workstation level.', 'N');
execute CreateSystemSetting('Scan Screens', 'CONVEYERBELTDELAY', '100', 'I', '100', 'N', 'N', 0, 60000, '', 'Time interval (in miliseconds) while conveyer belt controller port is maintained opened.', 'N');
execute CreateSystemSetting('Scan Screens', 'COUNTWASHESAT', 'I', 'S', 'I', 'N', 'N', 1, 1, 'I;O', 'The place where the number of washes are increased for a scanned unique item.'|| chr(10) ||'I = at inscan'|| chr(10) ||'O = at outscan', 'N');
execute CreateSystemSetting('Scan Screens', 'CRBDEFAULTPACKINGMODE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Define the default packing mode in CleanroomBatchPacking dialog:'|| chr(10) ||'0 =Per Batch'|| chr(10) ||'1 = Per customer', 'N');
execute CreateSystemSetting('Scan Screens', 'CRBPAIRSCANNING', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'New system setting to define if pair scanning is enabled.  If enabled, the button on outscanning may be activated', 'N');
execute CreateSystemSetting('Scan Screens', 'CRBPAIRSCANNINGACTIVE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'New system setting to define if pair scanning is enabled.  If enabled, the button on outscanning may be activated. The user either has to activate it manually or it will be activated automatically after scanning an item that is setup for pair scanning.'|| chr(10) ||'0 = No pair scanning enabled'|| chr(10) ||'1 = Pair scanning enabled manually'|| chr(10) ||'2 = Pair scanning enabled automatically'|| chr(10) ||'This setting replaces the CRBPAIRSCANNING system setting as of 9.03.04', 'N');
execute CreateSystemSetting('Scan Screens', 'CRBPAIRSCANNINGRULE', '1', 'I', '1', 'Y', 'N', 0, 1, '', 'New System setting to define the pair scanning rule if pair scanning is activated and a paired item is scanning'|| chr(10) ||''|| chr(10) ||'0 = Block'|| chr(10) ||'1 = Warn (Default 1)', 'N');
execute CreateSystemSetting('Scan Screens', 'CREATEDELIVNOTESTACKCHECK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the UHF stack check screen should automatically create outscans and a delivery note for customer related pool items.'|| chr(10) ||'0 = No'|| chr(10) ||'1 = Yes', 'N');
execute CreateSystemSetting('Scan Screens', 'DEFAULTROUTERETURNACTION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This controls if the route returns dialog automatically processes the previous garment scanned when a new garment is scanned'|| chr(10) ||''|| chr(10) ||'0 - No automatic processing, a warning message is shown that you did not process the previous garment'|| chr(10) ||'1 – Automatic processing, the previous garment scanned is processed To Stock using the 2 step process with status 80'|| chr(10) ||'2 - Automatic processing for unique items (so not smart barcodes), the previous garment scanned is processed To stock directly.  This also triggers the manual to stock button to process to stock directly.  Smart barcodes still take the 2 step approach.', 'N');
execute CreateSystemSetting('Scan Screens', 'DEFINEBATCHTREATMENT', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls at which moment the treatment is linked to a batch. Possible values:'|| chr(10) ||'0 = Treatment needs to be linked when creating the batch.'|| chr(10) ||'1 = Treatment will be linked to batch, after the batch is closed.', 'N');
execute CreateSystemSetting('Scan Screens', 'DELIVERYSCANONROUTEPRINT', '1', 'I', '1', 'N', 'N', 0, 1, '', 'This setting is only applicable if SCANBYROUTE = Yes.'|| chr(10) ||'0 = When printing the routelist the outstanding delivery scans (outstanding means not yet put on a delivery note) are linked to the route for which the routelist is being printed.'|| chr(10) ||'1 = Outstanding delivery scans are not linked to the route. This should be set when printing the routelist in advance.', 'N');
execute CreateSystemSetting('Scan Screens', 'FINALINSPECTIONREFRESH', '0', 'I', '0', 'N', 'N', 0, 10000, '', 'This setting defines the timeframe in milliseconds that controls how long the information of the scanned ID codes will be displayed, before the screen is cleared automatically (in case no errors occurred). After this interval has passed (and no errors were reported) then the screen is cleared automatically and the multi-read antenna(s) will start reading ID codes again (minimum refesh after1 millisecond, maximum 10 seconds, 0 means no automatic refresh).'|| chr(10) ||'This setting is only relevant when the module SORTINGSUPPORT is active and it will be used in combination with the system setting FINALINSPECTIONTIMEOUT.', 'N');
execute CreateSystemSetting('Scan Screens', 'FINALINSPECTIONTIMEOUT', '500', 'I', '500', 'N', 'N', 1, 10000, '', 'This setting defines the timeframe in milliseconds in which the multi-read antenna(s) can still read additional ID codes before the completeness check for this pile will be started. After this interval has passed the completeness check for the wearer this pile belongs to will be started (minimum timeout 1 millisecond, maximum 10 seconds).'|| chr(10) ||'This setting is only relevant when the module SORTINGSUPPORT is active and it will be used in combination with the system setting FINALINSPECTIONREFERESH.', 'N');
execute CreateSystemSetting('Scan Screens', 'GENERATEPNINSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, a button will appear at inscan multi read dialog to direct generate the packing note based on the inscans.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANALLOWHOURINTERVAL', '24', 'I', '24', 'N', 'Y', 0, 999, '', 'Number of hours that another inscan is not accepted for an already inscanned unique item.'|| chr(10) ||'Zero means no check. Typical use: 24 hours. (don''t allow to scan in twice at the same day)', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANBTCHCONFIRMADDCUST', 'N', 'B', 'N', 'N', 'N', null, null, '', 'For batch scanning inif this is Y and a customer is scanned who is not presently in the batch, a popup shows saying are you sure you want to add this customer to the batch.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANBUNDLE', '1', 'I', '1', 'N', 'N', 1, 2, '', '1 = When an item is scanned at bundle scan and it has not been scanned in then some of the processing done at inscan is done at bundle scan. Item is disconnected, a delivery variation is created and onsite inventory is updated.'|| chr(10) ||'2 = item that is not scanned in is not accepted.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANCONFIRMCUSTCHANGE', 'N', 'B', 'N', 'N', 'Y', null, null, '', 'When set a message is given in the inscan screen when customer of the scanned item differs from the customer of the previous scanned item. A question is asked ''Different customer accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated customer by customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANCONFIRMDEPTCHANGE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set a message is given in the inscan screen when department/customer of the scanned item differs from the department/customer of the previous scanned item. '|| chr(10) ||'A question is asked ''Different department accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated department by department.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANCONFIRMROUTECHANGE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set a message is given in the inscan screen when the route of the scanned item differs from the route of the previous scanned item. '|| chr(10) ||'A question is asked ''Different route accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated route by route.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANCOUNTBUTTON', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y then a button for soil count is visible in the inscan screen. This button starts the soil count entry per consumption point.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANCUSTOWNEDBUTTON', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y then a button for chip/barcode is visible in the inscan screen. This button starts the screen for making customer owned items unique.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANDISPLAYAREA', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Display in inscanning screen:'|| chr(10) ||'0 = Washing process'|| chr(10) ||'1 = Bank / locker', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANMAXBATCHQUANTITY', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'max number of items allowed in a treatment batch'|| chr(10) ||'If value = 0, then no check against max batch quantity', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANMAXBATCHWEIGHT', '0.0', 'F', '0.0', 'N', 'N', 0, 99999, '', 'It represents the maximum weight of a batch when in Inscan screen the items are scanned in batch. It has effect in Inscan screen only when > 0.', 'N');
execute CreateSystemSetting('Scan Screens', 'INSCANREJECTS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, via Inscan Multiread it is possible to scan in items as rejected by customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'MATINSCANREQUIRED', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'True = Storage scan screen will give an error message when a unique ID code is scanned that has not been scanned in.'|| chr(10) ||'False = If in storage scan a unique ID code is scanned that has not been scanned in it will be accepted.', 'N');
execute CreateSystemSetting('Scan Screens', 'MAXCOMPLETENESSDAYS', '100', 'I', '100', 'Y', 'N', 0, 999, '', 'This setting prevents that items that were lost in the plant (or delivered back to the customer without outscan) do not ''muddy the water''. All inscans older then the number of days configured with this setting are discarded in the completeness check. If they are found back and delivered after a couple of weeks, then there is no problem: the only effect will be that the number of pieces expected is not decreased by one. ', 'N');
execute CreateSystemSetting('Scan Screens', 'MULTIREADDISPLAYTIME', '5000', 'I', '5000', 'N', 'N', 0, 99999, '', 'Time in milliseconds that the colored bar at the screen that indicates that tags are being read remains visible after the last tag is scanned. When no more new tags are being scanned it can be assumed that all tags were scanned.', 'N');
execute CreateSystemSetting('Scan Screens', 'MULTIREAD_DEBUG_LEVEL', '0', 'I', '0', 'N', 'N', 0, 6, '1', 'It defines the level of detail for the logs generated by Multiread', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTCONFIRMPLANNEDROUTE', '1', 'I', '1', 'N', 'Y', 1, 3, '', 'This setting relates to the question that pops up when an item is outscanned that is planned for a different date/route then actual route.'|| chr(10) ||'1 : ask the user to switch to the planned route'|| chr(10) ||'2 : do not ask the user, always continue on PLANNED route'|| chr(10) ||'3 : do not ask the user, always continue on ACTUAL route', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANALLOWHOURINTERVAL', '24', 'I', '24', 'N', 'Y', 0, 999, '', 'Number of hours that another outscan is not accepted for an already outscanned unique item.'|| chr(10) ||'Zero means no check. Typical use: 24 hours. (don''t allow to scan out twice at the same day)', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANBTCHCONFIRMADDCUST', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'For batch scanning out, if this is Y and a customer is scanned who is not presently in the batch, a popup shows saying are you sure you want to add this customer to the batch.', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANCONFIRMCPLCHANGE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set a message is given in the outscan screen when consumption point of the scanned item differs from the consumption pointr of the previous scanned item. '|| chr(10) ||'A question is asked Different consumption point accept scan Y/N'|| chr(10) ||'Used when items need to be scanned / separated consumption point by consumption point', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANCONFIRMCUSTCHANGE', 'Y', 'B', 'Y', 'N', 'Y', null, null, '', 'When set a message is given in the outscan screen when customer of the scanned item differs from the customer of the previous scanned item. A question is asked ''Different customer accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated customer by customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANCONFIRMDEPTCHANGE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set a message is given in the outscan screen when department/customer of the scanned item differs from the department/customer of the previous scanned item. '|| chr(10) ||'A question is asked ''Different department accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated department by department.', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANCONFIRMROUTECHANGE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set a message is given in the outscan screen when the route of the scanned item differs from the route of the previous scanned item. '|| chr(10) ||'A question is asked ''Different route accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated route by route.', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANCONFIRMWEARERCHNG', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set a message is given in the outscan screen when the wearer number of the scanned item is smaller strict than the wearer number of the previous scanned item. '|| chr(10) ||'A question is asked ''Wearer number is out of sequence. Accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned in a sequence by wearer number.'|| chr(10) ||'The value of this system setting is the default value for a flag in customer screen.', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANPLANTDEPTCHECK', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If Y then you can only scan out customers belonging to the packing (plant) department of the workstation.'|| chr(10) ||'If N then you can scan any customer for the plant'|| chr(10) ||''|| chr(10) ||'Only applicable for module BATCHJOB', 'N');
execute CreateSystemSetting('Scan Screens', 'OUTSCANWEARERCHNGMETHOD', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This system setting must be used in combination with the other system setting OUTSCANCONFIRMWEARERCHNG. '|| chr(10) ||'1 - if the the wearer number of the current scanned item is smaller than the wearer number of the previously scanned item then show confirmation message.'|| chr(10) ||'2 - the wearer number of the current scanned item is different than the wearer number of the previously scanned item then show confirmation message. ', 'N');
execute CreateSystemSetting('Scan Screens', 'OVERFLOWSORTADDRESS', '01', 'S', '01', 'N', 'N', 2, 2, '', 'Setting for customers that use digisort : if the destination rail could not be determined the value of this system setting is send to the sortingsytem.', 'N');
execute CreateSystemSetting('Scan Screens', 'PRINTLABELSTDMAT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'False = no label is printed from Outscan Bulk Put Up Per Route screen for standard mats.'|| chr(10) ||'True = a label per customer is printed from Outscan Bulk Put Up Per Route for standard mats.', 'N');
execute CreateSystemSetting('Scan Screens', 'PRINTMATREPORTAUTO', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Depending on the System Setting "PrintMatReportAutomatically", a report for the currently scanned mat will be printed:'|| chr(10) ||'-	Value 0 : for the standard mats print the report "", for the LOGO mats print the report ""'|| chr(10) ||'-	Value 1 : only for LOGO mats the report is automatically  printed : ""'|| chr(10) ||'-	Value 2 : no report is automatically printed.', 'N');
execute CreateSystemSetting('Scan Screens', 'PROCESSDELNOTESORTSYSTEM', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Never process / print deliverynote automatic, user must press the process / print button'|| chr(10) ||'1 = Process / print deliverynote automatic when no packingnote found (packingnote was created in step 3).'|| chr(10) ||'2 = Always process / print deliverynote automatic'|| chr(10) ||'With option 1 and 2 the delivery note is processed and printed when a deliveryscan is detected with a different customer, department or distribution point, then the previous one is closed and a new one is started. The button still remains available in case at the end of the day no deliveryscans are made or a split is required.'|| chr(10) ||'Only used for module TSPACKING.', 'N');
execute CreateSystemSetting('Scan Screens', 'PWBINSCANCONFCUSTCHANGE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set a message is given in the PWB inscan screen when customer of the scanned item differs from the customer of the previous scanned item. A question is asked ''Different customer accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated customer by customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'PWBOUTSCANCONFCUSTCHANGE', 'N', 'B', 'Y', 'Y', 'N', null, null, '', 'When set a message is given in the PWB outscan screen when customer of the scanned item differs from the customer of the previous scanned item. A question is asked ''Different customer accept scan Y/N''.'|| chr(10) ||'Used when items need to be scanned / separated customer by customer.', 'N');
execute CreateSystemSetting('Scan Screens', 'RAGINBATCHSELECTION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = from to customer selection (default) '|| chr(10) ||'1 = single customer selection', 'N');
execute CreateSystemSetting('Scan Screens', 'RECEIVESCANUSEVIRTBUNDLE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the on-site receive scan at customers of the laundry uses the same virtual bundle mechanism as the outscan at the laundry, to improve accuracy of reading.'|| chr(10) ||'0=No'|| chr(10) ||'1=Yes'|| chr(10) ||'When enabled it will use the same setting (UHFOUTSCANBUNDLEPERC) as the delivery note dialog does.'|| chr(10) ||'This setting is only applicable for module UHF Complete Bundle Outscan.', 'N');
execute CreateSystemSetting('Scan Screens', 'REGIONALFONTNAME', 'Noto Sans', 'S', 'Noto Sans', 'N', 'N', null, null, '', 'This setting is intended to be used for multiread screens for displaying correctly the characters in CJK languages (chinese, japanese, korean).'|| chr(10) ||'This works together with a setting available on client folder, absclient.properties: Fonts=[Abssolute_PATH]\\client\\fonts'|| chr(10) ||'Possible fonts are: Noto Sans, MS Mincho', 'N');
execute CreateSystemSetting('Scan Screens', 'REISSUERAGGEDITEM', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When this system setting = ''Y'' it is possible to re-issue a ragged unique item during inscan.', 'N');
execute CreateSystemSetting('Scan Screens', 'RESERVEBOXFORSPECIALSCAN', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for customer residential setting:'|| chr(10) ||'Y = The boxes for the special scans are reserved at soil receiving; it is used only when SPECIALRESIDENTIALSCANS is in the licese'|| chr(10) ||'N = The boxes for the special scans are not reserved at soil receiving.', 'N');
execute CreateSystemSetting('Scan Screens', 'RETURNDELIVERYSCAN', '0', 'I', '1', 'N', 'N', 0, 1, '', 'When set to 1 and an item that has been scanned out is scanned in rewash or at checkpointscan and the outscan is not yet assigned to a packingnote then the delivery scan is deleted, meaning that the outscan is cancelled and will not be put on a packingnote. Scans that are already on a packingnote remain untouched.'|| chr(10) ||'Note: in repair scan the delivery scan is always cancelled when not assigned to a packingnote, so disregarding this systemsetting.', 'N');
execute CreateSystemSetting('Scan Screens', 'REWASHDAYINTERVAL', '0', 'I', '0', 'N', 'N', 0, 99, '', 'Rewash scan: Interval for which is checked if there is already a rewash registered for the scanned item. When set to 0, no check is done on rewash day interval. The message is a warning, it is still possible to register the rewash.', 'N');
execute CreateSystemSetting('Scan Screens', 'REWASHMAX', '0', 'I', '0', 'N', 'N', 0, 999, '', 'Rewash screen: define maximum number of rewashes allowed for 1 item. When an item exceeds the maximum number of rewashes, a warning is shown. It is still allowed to register the rewash. When set to 0, no check on max rewashes is done.', 'N');
execute CreateSystemSetting('Scan Screens', 'REWASHSCANTIMEINTERVAL', '30', 'I', '30', 'N', 'N', 0, 9999, '', 'Time interval in minutes for multi read rewash scan screen. Items scanned within the interval will not be processed.  Setting only applicable to multiread rewash screen, so not to single read rewash screen.', 'N');
execute CreateSystemSetting('Scan Screens', 'SCANBYROUTE', 'N', 'B', 'N', 'N', 'Y', null, null, '', 'If set then in all scan screens the route is shown. The incomming route and outgoing route is determined,'|| chr(10) ||'and completeness check per route is possible.', 'N');
execute CreateSystemSetting('Scan Screens', 'SCANINTERNALBU', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting can be used to manage inscan items from processing business unit and from internal processing business unit for garments.'|| chr(10) ||'The system setting is used only in combination with INTERNALCALC module.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Inscan is allowed from internal processing business unit and from processing business unit'|| chr(10) ||'1 = Inscan is allowed only from internal processing business unit'|| chr(10) ||'2 = Inscan is allowed from internal processing business unit.For inscan from processing business unit the user can choose if the scan will be denied or accepted', 'N');
execute CreateSystemSetting('Scan Screens', 'SCANMESSAGETIME', '500', 'I', '500', 'N', 'Y', 100, 3000, '', 'Indicates how long (in milliseconds) the ''Scan Ok'' message should stay on the screen in scan programs. During this time the user cannot scan the next item.', 'N');
execute CreateSystemSetting('Scan Screens', 'SHIPMENTCHECKPERDELNOTE', '1', 'I', '1', 'N', 'N', 0, 1, '', 'Defines for send to laundry and receive from laundry scan screens (also for the mobile version in Linen Assistant*) if items that are not outscanned via the ABSSolute application should be accepted or not.'|| chr(10) ||'0 = No check, always accept'|| chr(10) ||'1 = Check and reject scan if not outscanned.'|| chr(10) ||'When 0 then reporting on qty delivered vs. qty received cannot be done on delivery note level.'|| chr(10) ||'When 0 pool items that were not outscanned will automatically be linked to same customer as other items that are scanned simultaneously.'|| chr(10) ||'*) From version 6 of Linen Assistant the check aspect of this setting is overruled in case on the device is configured ''Manually select delivery notes'' or ''Select a single deliverynote by scanning''. In those cases the PDA only accepts items scanned out at the selected delivery note(s).', 'N');
execute CreateSystemSetting('Scan Screens', 'SHOWPRODUCT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Show product description:'|| chr(10) ||'0 = Normal'|| chr(10) ||'1 = Show product description large.'|| chr(10) ||'This setting is used in outscan and in outscan/sort (residential) screens only.', 'N');
execute CreateSystemSetting('Scan Screens', 'SIMULATEINSCAN', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No inscan is simulated'|| chr(10) ||'1 = When an item is scanned out without being scanned in, an inscan is simulated that has the creation timestamp of the client delivery note as its scan timestamp.'|| chr(10) ||'2 = When an item is scanned out without being scanned in, an inscan is simulated that will have a scan timestamp that will be greater than or equal to the batch creation timestamp up till a maximum of 3 hours after the batch was created. The timestamp will be taken randomly from within this 3 hour interval. (residential only)'|| chr(10) ||'This setting is both for residential and garments. For residential define a workstation with code ''SIMULATEIN''. For garments define a workstation with code ''SIMULATEINGM''. For garments the inscan is only created if the workstation is defined. Option 1 and 2 are the same for garments.', 'N');
execute CreateSystemSetting('Scan Screens', 'STACKCHKPERSONALIZEDMIXED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'System setting only used for the Stack Check dialog. When set to No it is not possible to have different personalized garment products in the stack. When set to Yes, the check on mixed products is skipped when there is at least one personalized garment product in the stack.', 'N');
execute CreateSystemSetting('Scan Screens', 'STACKCHPERSONALIZEDBUNDLE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Only used for multiread stack check scan screen. When set to Yes, always a virtual bundle is created for an accepted stack. When set to No, no virtual bundle is created if the accepted stack contains at least one personalized garment product.', 'N');
execute CreateSystemSetting('Scan Screens', 'STORAGESCANASSIGN', '1', 'I', '1', 'N', 'N', 1, 3, '', '1 = System determines the active stock location on which a unique item will be stored. This cannot be changed by the user.'|| chr(10) ||'2 = The user must scan the active stock location on which a unique item will be stored. There will be no default.'|| chr(10) ||'3 = The system determines the active stock location, but the user can change this. This setting is only available when licensed.', 'N');
execute CreateSystemSetting('Scan Screens', 'TOUCHSCREENBUTTONSCOLUMN', '0', 'I', '0', 'N', 'N', 0, 6, '', 'When = 0, the buttons on Soil Count per Consumption Point are displayed as defined in the touchscreenbutton application. When the value is between 1 and 6, the value determines how many columns are displayed on the screen, e.g. a value of 4 means 4 columns.', 'N');
execute CreateSystemSetting('Scan Screens', 'TOUCHSCREENBUTTONSROW', '0', 'I', '0', 'N', 'N', 0, 5, '', 'When = 0, the buttons on Soil Count per Consumption Point are displayed as defined in the touchscreenbutton application. When the value is between 1 and 5, the value determines how many rows are displayed on the screen, e.g. a value of 4 means 4 rows.', 'N');
execute CreateSystemSetting('Scan Screens', 'TSPACKINGUSAGE', '0', 'I', '0', 'N', 'Y', 0, 2, '', 'Depending on the systemsetting TSPACKINGUSAGE the scans can be put on an existing packingnote, or can be put on a separate, new created packingnote:'|| chr(10) ||'0 = Scans are added on an existing note, if it exists. All lines are shown.'|| chr(10) ||'1 = Scans are added on an existing note, if it exists. Only the scans are shown on the screen, all other lines are hidden.'|| chr(10) ||'2 = Scans are always put on a separate, new created packingnote.'|| chr(10) ||'Only used for module TSPACKING.', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFHRSNOINSCANAFTRDELNOTE', '0', 'I', '0', 'N', 'N', 0, 9999, '', 'Defines time interval in number of hours in which items or containers with UHF tags are rejected when inscanned or scanned into a production buffer after being processed on a delivery note, taking into account plant operation hours.'|| chr(10) ||''|| chr(10) ||'Value 0 means this check is not performed.'|| chr(10) ||''|| chr(10) ||'Usecase: when UHF readers at loading dock should only scan returning items, not shipped items.'|| chr(10) ||''|| chr(10) ||'Interval calculation: from moment of processing delivery note until moment of scanning minus time the plant was not operating.', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFINSCANTRACKINGONLY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if UHF multiread inscans cause any delivery variations or decrease on-site inventory.'|| chr(10) ||'When set to Y then the UHF multiread inscan can be used while the same items are soil counted as well. In this case only soilcounts cause the creation of delivery variations and the decrease of on-site inventory.'|| chr(10) ||'When set to N then UHF multiread inscans do cause creation of delivery variations are decreasing on-site inventory.'|| chr(10) ||'Related settings: UHFPOOLITEMSTARTUPPHASE and UHFPOOLITEMSTARTUPCALC in Delivery Note settings group to define if UHF outscans should have any effect on delivered quantity.', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFISSUEPOOLCOMBINERAG', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'N = standard - not possible to rag and assign in Work order status control - pool items'|| chr(10) ||'Y = possible to rag and assign in Work order status control - pool items', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFMONITORDAYSNOTSEENLIMT', '14', 'I', '14', 'N', 'N', 1, 24, '', 'Defines the number of days after which unique items are ignored in the UHF monitor buffer view.'|| chr(10) ||'The buffer size will not include items that have not been scanned for X days, X is defined by this system setting.', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFMONITORGRAPHTIMEWINDOW', '8', 'I', '8', 'N', 'N', 1, 24, '', 'Defines the time window for the graph in the UHF monitor screen.'|| chr(10) ||'The graph shows data for a rolling window of last X hours, where X is defined by this system setting.', 'N');
execute CreateSystemSetting('Scan Screens', 'UHFOUTSCANTRACKINGONLY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if UHF multiread outscan pool at deliverynote affects delivered quantities and can cause any delivery variations (if item was not yet scanned in) or increase of on-site inventory.'|| chr(10) ||'When set to Y then only scan transactions are created and uniqueitems are updated.'|| chr(10) ||'When set to N then UHF outscan pool at deliverynote does update delivered quantities at the delivery note. In this case UHFSTARTUPPHASE setting is applicable.'|| chr(10) ||'Related settings: UHFINSCANTRACKINGONLY'|| chr(10) ||'Setting is only valid for v8.03.12k and v9.00.04 and up', 'N');
execute CreateSystemSetting('Scan Screens', 'UNEXPALLOWANCECRBOUTSCAN', '0', 'I', '0', 'Y', 'N', 0, 3, '', 'Setting to control what unexpected items are allowed within a clean room batch and what are not. Will be used in combination with UNEXPECTEDUIATCRBOUTSCAN. Possible values:'|| chr(10) ||'0 = Allow outscan for bill to customer'|| chr(10) ||'1 = Allow outscan for the same customer'|| chr(10) ||'2 = Allow outscan for the same department'|| chr(10) ||'3 = Allow outscan for the same consumption point', 'N');
execute CreateSystemSetting('Scan Screens', 'UNEXPECTEDUIATCRBOUTSCAN', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0- Reject the scan if the item is not scanned or counted in  with the current cleanroombatch'|| chr(10) ||'1- User can reject or accept the scan'|| chr(10) ||'2- Accept the scan', 'N');
execute CreateSystemSetting('Scan Screens', 'URIFILTERVALUE', '1', 'I', '1', 'N', 'N', 0, 8, '', 'UHF tag IDs can be shown as their EPC hex code or as Tag URI code, when SGTIN-96 encoding is used.'|| chr(10) ||'The URI code is consists of 3 parts : company prefix, item reference and serial number.'|| chr(10) ||'Those parts are separated with a dot.'|| chr(10) ||''|| chr(10) ||'In order to convert from a URI-code to a EPC hex code one additional piece of information is required: the contents of the filtervalue segment.  This setting configures the filtervalue.'|| chr(10) ||'Only applicable when USEURICODE = 1', 'N');
execute CreateSystemSetting('Scan Screens', 'USEUHFTAGFLTERFORIPANDCOM', 'N', 'B', 'N', 'N', 'N', null, null, '', 'N = no tag filters'|| chr(10) ||'Y = apply UHF tag filters to tag data recieved from com port or TCP/IP scanners'|| chr(10) ||''|| chr(10) ||'NOTE: this applies to multi and single read, but only for tags of 24 characters (UHF tags)', 'N');
execute CreateSystemSetting('Scan Screens', 'USEURICODE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'UHF tag IDs can be shown as their EPC hex code or as Tag URI code, when SGTIN-96 encoding is used.'|| chr(10) ||'The URI code is consists of 3 parts : company prefix, item reference and serial number.'|| chr(10) ||'Those parts are separated with a dot.'|| chr(10) ||''|| chr(10) ||'0 = No, UHF tag ID''s are shown as EPC hex code (standard)'|| chr(10) ||'1 = Yes, UHF tag ID''s are shown as URI code.'|| chr(10) ||'When this setting = 1  the URI code is displayed and can be manually entered in single read garment scan screens. URI code is shown in scan field, at several garment reports and in garments per wearer.', 'N');
execute CreateSystemSetting('General', 'ABSDOSWRITECWEIGHTHIST', 'N', 'B', 'N', 'N', 'Y', null, null, '', 'Defines if the CLEAN weighingticket during processing should write in the historical table of the ABS DOS system the CLEAN weights.', 'N');
execute CreateSystemSetting('General', 'ABSDOSWRITEDELHISTORY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the deliverynote during processing should write in the historical table of the ABS DOS system the delivered pieces and shortages.', 'N');
execute CreateSystemSetting('General', 'ABSDOSWRITESWEIGHTHIST', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the SOIL weighingticket during processing should write in the historical table of the ABS DOS system the SOIL weights.', 'N');
execute CreateSystemSetting('General', 'ACTIONFORBRINGSTOPS', '0', 'I', '0', 'N', 'N', 0, 3, '', 'If a stop is type Bring and there is no delivery then depending on this setting the following can be done:'|| chr(10) ||'0 = No action (i.e. the stop appears on the routelist)'|| chr(10) ||'1 = If there is no delivery for a bring stop then cancel the stop (stop gets status cancelled, it will not appear on the routelist)'|| chr(10) ||'2 = If there is no delivery for a bring stop then delete the stop'|| chr(10) ||'3 = If there is no delivery for a bring stop then ask the user whether the stop can be cancelled.', 'N');
execute CreateSystemSetting('General', 'ACTIVITYLONGDESC', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if it is allowed to define a long description for an activity. Possible values:'|| chr(10) ||'0 - Do not show this field at all'|| chr(10) ||'1 - Do show the field but it is not obligated to fill in a long activity description'|| chr(10) ||'2 - Do show the field and it is mandatory to fill in a long activity description', 'N');
execute CreateSystemSetting('General', 'ADDCONTACTWITHNODELSCHEME', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if you are allowed to create a new contact message for a customer that has no delivery scheme.'|| chr(10) ||''|| chr(10) ||'0 = yes, a contact can be added if the customer has no delivery scheme'|| chr(10) ||'1 = no, this is blocked, only customers with delivery scheme can have a new contact added - see note below for one exception'|| chr(10) ||''|| chr(10) ||'This is used for laundries in the US where contacts are dealt with only on the route assistant.  So contacts for customers with no delivery scheme (so head office bill to only style customers) will never be processed.'|| chr(10) ||''|| chr(10) ||'NOTE: a master or contract owning customer without a delivery scheme but you are creating linked contacts for its child customers is the one exception for setting 1', 'N');
execute CreateSystemSetting('General', 'ALLOWALLPRODDELVAR', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Depending on this setting, the user is allowed to either select all active products when manually creating a delivery variation or only those products that are defined in the PLPC or only products from selected Consumption point.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Only products from PLPC may be selected'|| chr(10) ||'1 - All active products may be selected'|| chr(10) ||'2 - Only products from selected consumption point may be selected.'|| chr(10) ||''|| chr(10) ||'When defined as a default value, the user has the possibility to overrule the default as provided by the system when adding a delivery variation. When defined as a fixed value, the user cannot overrule this setting.', 'N');
execute CreateSystemSetting('General', 'ALLOWCONTUSEBYOTHERBU', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Default value for the field ''Can be used by Other Business Units'' in the container screen. '|| chr(10) ||'When set the containers can be used by all business units although they are owned by a specific business unit.', 'N');
execute CreateSystemSetting('General', 'ALLOWDELETECONTACTMESSAGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if it is allowed to delete any contacts via the Contact Manager dialog. Possible values:'|| chr(10) ||'0 = Do not allow to delete any contacts at all'|| chr(10) ||'1 = Do allow to delete any contacts, taking into account the defined access rights at user level.'|| chr(10) ||'When set to 1 then a regular system user may only delete his own contacts, while a system user that has full contact manager access may delete also contacts created by any other system user', 'N');
execute CreateSystemSetting('General', 'ALLOWDELETEPRICELIST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it should be possible to physically delete a contract price list including its prices from within the Contract dialog when it is not used by any customer. Possible values:'|| chr(10) ||'0 - It is not possible to physically delete a contract price list (default) '|| chr(10) ||'1 - It is possible to physically delete a contract prive list'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the MASTERACCOUNTMANAGEMENT module is in the license.', 'N');
execute CreateSystemSetting('General', 'ALLOWDISCONNECTPRICELIST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it should be possible to disconnect a contract price list from a contract while allowing it to stay connected to a customer on customer price list level and keeping it acive as a general price list. Possible values:'|| chr(10) ||'0 - It is not possible to disconnect a contract price list from a contract (default) '|| chr(10) ||'1 - It is possible to disconnect a contract price list from a contract'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the MASTERACCOUNTMANAGEMENT module is in the license.', 'N');
execute CreateSystemSetting('General', 'ALLOWGARMENTPRODUCTCONV', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'System setting used in Customer Product Conversion dialog for enabling Product Conversion radio button for Garments.', 'N');
execute CreateSystemSetting('General', 'ALLOWLINENPRODUCTCONV', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'System setting used in Customer Product Conversion dialog for enabling Product Conversion radio button for Linen.', 'N');
execute CreateSystemSetting('General', 'ALLOWMODIFYCONTACTNOTES', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if it is allowed to modify any initial contact notes via the Contact Manager dialog. Possible values:'|| chr(10) ||'0 = Do allow to modify any contact notes considering the defined access rights at user level'|| chr(10) ||'1 = Do only allow to modify contact notes by the user who created the contact'|| chr(10) ||'2 = Do NOT allow to modify the contact notes once the initial contact is saved'|| chr(10) ||'When set to 0 then a regular system user may only modify his own contact notes, while a system user that has full contact manager access may modify also contact notes created by any other system user.', 'N');
execute CreateSystemSetting('General', 'ALLOWORPACKPRODUCTCONV', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'System setting used in Customer Product Conversion dialog for enabling Product Conversion radio button for OR Packs.', 'N');
execute CreateSystemSetting('General', 'ALLOWSUPPLPRODUCTSEARCH', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Via this setting it can be controlled if it should be possible to search for a product, based on the supplier product code in the standard product search control. Please keep in mind that multiple laundry products can be linked to the same supplier product code.  Possible values:'|| chr(10) ||'0 - Do not allow to search based on supplier product code (default)'|| chr(10) ||'1 - Allow to search for a product based on supplier product code', 'N');
execute CreateSystemSetting('General', 'ALLOWUNDELIVROUTECHECKIN', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls the button in WebX route check in stops screen where you can change a visit status of a stop to or from undeliverable.'|| chr(10) ||''|| chr(10) ||'0 = Can change the visit status from delivered to undeliverable and visa versa'|| chr(10) ||'1 = Can only change from undeliverable to delivered.  Making a stop undelivered is not allowed.  So is disabled if the stop is delivered', 'N');
execute CreateSystemSetting('General', 'AUTOADDDEFREPLACEMENTPL', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This controls the automatic adding of the default global replacement price list when the contract is created.  It also controls if the user is allow to remove or end date this price list.'|| chr(10) ||'0 = do nothing'|| chr(10) ||'1 = when creating a new contract, automatically add the default replacement price list for the contracts currency.'|| chr(10) ||'2 = when creating a new contract, automatically add the default replacement price list for the contracts currency and block the removal or end dating of it', 'N');
execute CreateSystemSetting('General', 'AUTOCREATECUSTCHILDOBJECT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if any child objects (e.g. delivery points, cost centers, departments and consumption points) belonging to the customer master object will have to be added manually via the ERP Customer Integration dialog, or if they will be added automatically when adding a customer via this dialog. This implies that in the latter case all child objects are already known at the moment the customer is added manually and are also included in their respective import tables. Possible values:'|| chr(10) ||'0 = Manually add the child objects'|| chr(10) ||'1 = Automatically add the child objects when adding their customer'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module ERPINTEGRATION is active.', 'N');
execute CreateSystemSetting('General', 'AUTOGENERATEDROUTEDOC', 'AAAA', 'S', 'AAA', 'N', 'N', null, null, 'ABC', 'This defines the merging of the automatically generated route documents into combined pdfs'|| chr(10) ||'Each of the 3 characters affects different documents'|| chr(10) ||''|| chr(10) ||'Character 1 is for putup docs '|| chr(10) ||'Character 2 is for invoices'|| chr(10) ||'Character 3 is for soil reasonability reports'|| chr(10) ||''|| chr(10) ||'With values'|| chr(10) ||'  A = No merging - documents per route and date (and by stop if for invoices)'|| chr(10) ||'  B = Merge by depot and date in route order'|| chr(10) ||'  C = Merge by date in depot and route order'|| chr(10) ||''|| chr(10) ||'So a setting of ABC would mean that:'|| chr(10) ||''|| chr(10) ||'A) For putup docs, a PDF is generated per document type, route and date'|| chr(10) ||'B) For invoices, a PDF is generated per document type, depot and date, sorted within the merged pdf in route and stop order'|| chr(10) ||'C) For soil reasonability reports, a PDF is generated per date and sorted withing the merged pdf by route', 'N');
execute CreateSystemSetting('General', 'AUTOGENERATEROUTECONTROL', '0', 'I', '0', 'N', 'N', 0, 5, '1', 'This is the number of working days after the route driving date that the route control record for the following week should be automatically generated by the scheduled process if its not already created by another process.  '|| chr(10) ||''|| chr(10) ||'0 = don''t generate'|| chr(10) ||'1 - 5 = number of working days after to autogenerate the following weeks route control record.'|| chr(10) ||''|| chr(10) ||'NOTE: This is working days so a Friday route with a system of 2 would have the next weeks route control generated on Tuesday.', 'N');
execute CreateSystemSetting('General', 'AUTOMATICPUTUPDOCFINALISE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting is used to control if packing notes are finalised to delivery notes when generating from the web service call.'|| chr(10) ||''|| chr(10) ||'0 = Don''t finalise'|| chr(10) ||'1 = Finalise to delivery notes'|| chr(10) ||''|| chr(10) ||'NOTE: This replaces the workstation setting of FinalizeDeliveryNote that is used for this in the client.'|| chr(10) ||''|| chr(10) ||'This is also used in the automatic assign not linked packing notes in direct invoice generation to automatically finalize when assigned', 'N');
execute CreateSystemSetting('General', 'AUTOMATICSOILPROCESSING', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Defines if soil tickets are automatically processed to create delivery variations and marked as completed for the previous weeks route when generated put up docs for the next week of the route.'|| chr(10) ||'0 = no'|| chr(10) ||'1 = yes', 'N');
execute CreateSystemSetting('General', 'AUTOSETTLEMENTOPTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting is used by the scheduled automatic settlement process'|| chr(10) ||''|| chr(10) ||'0 = do not settle the route if there are route transactions pending approval'|| chr(10) ||'1 = settle the route if there are route transactions pending approval by first automatically setting these as approved'|| chr(10) ||''|| chr(10) ||'NOTE: This is not used by the manual settlement process or the scheduled settlement of previous weeks routes as that already automatically approves transactions', 'N');
execute CreateSystemSetting('General', 'AVERAGEBASEDCALC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Only used in module AVERAGEBASEDSTANDARDS'|| chr(10) ||'0 = Average is calculated based on standard delivery and variation amount'|| chr(10) ||'1 = Average is calculated based on delivered amounts', 'N');
execute CreateSystemSetting('General', 'BIUSERISSYSTEMUSER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This controls the type of user can be created for BI Access Rights'|| chr(10) ||''|| chr(10) ||'0 = BI users can be created from system users or stand alone from the BI Access Rights dialog'|| chr(10) ||''|| chr(10) ||'1 = BI users can only be created from system users (so you cannot create BI users that are stand alone)', 'N');
execute CreateSystemSetting('General', 'BULKPUTUPSORTING', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This system setting is used to identify how the BulkPutUp report is sorted. '|| chr(10) ||''|| chr(10) ||'0 = The bulk put up rpt sorts based on packing department, then route and has a page break after the route, so multiple packing departments could be on the same page.'|| chr(10) ||''|| chr(10) ||'1 = The bulk put up rpt sorts based on route, then packing department with the page break after each route. This allows multiple packing departments from a route to be on the same page. '|| chr(10) ||''|| chr(10) ||'The sort would not be configurable.', 'N');
execute CreateSystemSetting('General', 'CHANGELOCATIONADDRESS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if plant and depot location addresses can be edited.  This is used when these addresses are controlled by an interface, not the client screens.'|| chr(10) ||'0 = can be edited'|| chr(10) ||'1 = cannot be edited'|| chr(10) ||''|| chr(10) ||'this applies to the address 1, 2, city, county, state, zip, county and if visible, Tax Area ID fields', 'N');
execute CreateSystemSetting('General', 'CHARGEDELIVERYFEE', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Default value for routestop:'|| chr(10) ||'0 = No delivery fee'|| chr(10) ||'1 = Normal delivery fee'|| chr(10) ||'2 = Special delivery fee', 'N');
execute CreateSystemSetting('General', 'CHECKONSITEINVLIMIT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set the following check is done: for products with type of merchandize = non-garments, having in product list per customer billing method 1, fixed rent quantity, it is checked in delivery variations and delivery note screen, when adding a new line or changing the quantity, that the onsiteinventory at the current date does not exceed the fixed rent quantity. If it does an error message is given and the user is not allowed to make the change.', 'N');
execute CreateSystemSetting('General', 'CHECKONSITEINVLIMIT3', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set the following check is done: for products having billing method 3 (=circulating inventory) it is checked in delivery variations and delivery note screen, when adding a new line or changing the quantity, that the onsite inventory at the current date does not exceed the circulating inventory quantity. If it does an error message is given and the user is not allowed to make the change.', 'N');
execute CreateSystemSetting('General', 'CHECKSALESTOPURCHASEPRICE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'for works order (sales) and sales order (trade module)'|| chr(10) ||''|| chr(10) ||'= 0  no check (default)'|| chr(10) ||'= 1 check sales price to purchase price for the default supplier (taking supplier from stockdefinitionperitem then plpc then product and including exchange rate if different currency) and warn if sales price is lower than purchase price'|| chr(10) ||'= 2  same check as option 1 but do not allow saving of record', 'N');
execute CreateSystemSetting('General', 'CHGCONTRACTFIELD', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether it will be possible to change some predefined contract fields (Duration and Terms of Notice) that are normally not editable since they will be filled automatically by the application. In some situations, the user should be able to override the standard values for these fixed fields. Possible values:'|| chr(10) ||'0 - Do not allow to change these predefined contract fields'|| chr(10) ||'1 - Do allow to change these fixed contract field.'|| chr(10) ||'2 - Make termination date editable'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the MASTERACCOUNTMANAGEMENT module is active.', 'N');
execute CreateSystemSetting('General', 'CHUNKSIZEROWLOAD', '500', 'I', '500', 'N', 'N', 100, 50000, '', 'Defines the number of rows that are loaded in a grid when pressing the load more button. '|| chr(10) ||'Each time the load more button is pressed this number of rows is loaded. Initially the grid is loaded with this number or rows.'|| chr(10) ||'This setting replaces the setting in the pull down menu under View # of Records.'|| chr(10) ||'For WAN environments this setting better be small, for LAN environments this setting can be higher.', 'N');
execute CreateSystemSetting('General', 'CLEANUPDELIVERYSCANS', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This setting is used in combination with a scheduled process for cleaning up delivery scans. The value is the number of weeks after which delivery scans are removed by this scheduled process. When set to 0, they will not be removed.', 'N');
execute CreateSystemSetting('General', 'CLEANUPLOGDAYS', '30', 'I', '30', 'N', 'N', 1, 999, '', 'Minimum number of days where log messages need to be kept. Older messages will be deleted by the clean up scheduled process', 'N');
execute CreateSystemSetting('General', 'CLEANUPPROCESSLOGDAYS', '30', 'I', '30', 'N', 'N', 1, 999, '', 'Minimum number of days where process log messages need to be kept. Older messages will be deleted by the clean up scheduled process', 'N');
execute CreateSystemSetting('General', 'COMMISSIONEXTENSION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Standard'|| chr(10) ||'1 = Extended'|| chr(10) ||'Only used for module Commission', 'N');
execute CreateSystemSetting('General', 'COMPANYCODE', '000', 'S', '000', 'N', 'N', 3, 3, '', 'This company code will be exported in the GL (General Ledger) interface with US bookkeeping systems.'|| chr(10) ||'The company code will end up in seqment4 of the account string.', 'N');
execute CreateSystemSetting('General', 'CONSIGNMENTNOTEPROCEDURE', '1', 'I', '1', 'N', 'N', 1, 3, '', 'This setting controls which delivery notes will be collected on a consignment note. Possible values:'|| chr(10) ||'1 - To date (= standard method). All delivery notes that have a delivery date smaller than or equal to the selected date will be collected on the consignment note.'|| chr(10) ||'2 -  Today. All delivery notes that have a delivery day that equals the selected date will be collected on the consigment note.'|| chr(10) ||'3 - All delivery notes that have not been linked to a consignment note yet will be collected on the consignment note.This includes also (future) delivery notes with a delivery date > selected date.', 'N');
execute CreateSystemSetting('General', 'CONTACTAUTOCLOSEDELAY', '1', 'I', '1', 'N', 'N', 0, 9999, '', 'Number of days after status complete that a low priority or no follow-up contact (regardless of priority) is automatically closed'|| chr(10) ||'Default =  1', 'N');
execute CreateSystemSetting('General', 'CONTACTCUSTOMERCOMS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This enables the customer communication contact category and customer communication name field for followup notes'|| chr(10) ||''|| chr(10) ||'0 = do not show option'|| chr(10) ||'1 = show option', 'N');
execute CreateSystemSetting('General', 'CONTACTFOLLOWUPBY', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This defines if the follow-up by radio button defaults to user or by driver'|| chr(10) ||'This was defined by the presence of the module ROUTEASSISTANT but is not controlled by this setting'|| chr(10) ||'0 = follow-up by route'|| chr(10) ||'1 = follow-up by user'|| chr(10) ||''|| chr(10) ||'note, this applies to contacts created from the client and web portal', 'N');
execute CreateSystemSetting('General', 'CONTACTFOLLOWUPDAYS', '0', 'I', '0', 'Y', 'N', 0, 45, '', 'This setting defines the number of days in advance that will be used to calculate the follow update starting at the moment the contact is created. A value of 0 indicates that the default follow up date will be the current date.'|| chr(10) ||''|| chr(10) ||'This setting will be used in combination with CONTACTFOLLOWUPTIME to determine the default follow up date and time (when applicable)'|| chr(10) ||''|| chr(10) ||'When defined as a fixed default, then the default value cannot be overruled by any user upon creation of a new contact nor may it be changed when modifying it afterwards.', 'N');
execute CreateSystemSetting('General', 'CONTACTFOLLOWUPTIME', '0', 'I', '0', 'N', 'N', 0, 24, '', 'This setting controls if the time is considered relevant when defining a follow up date (or date and time) for a contact to be shown on the RA or in the windows client.'|| chr(10) ||'When 0, then the time is considered irrelevant and no time field will be shown in the windows client or on the RA.'|| chr(10) ||'When > 0, then this is the time (hour) after midnight the contact is supposed to be followed up.'|| chr(10) ||'This setting will be used in combination with CONTACTFOLLOWUPDAYS to determine the default follow up date and time (when applicable)', 'N');
execute CreateSystemSetting('General', 'CONTACTMAXFILES', '5', 'I', '5', 'N', 'N', 0, 10, '', 'This system setting defines the maximum number of files that may be attached to a single contact message via the client application or the web portal. A value 0 means that no files may be added to a contact message. This setting will be used in combination with CONTACTMAXFILESIZE and CONTACTMAXTOTALFILESIZE to determine whether any (additional) files may be added or not.', 'N');
execute CreateSystemSetting('General', 'CONTACTMAXFILESIZE', '20', 'I', '20', 'N', 'N', 0, 20, '', 'This system setting defines the maximum size in MB for a single file that may be attached to a contact message via the client application or the web portal. A value 0 implies that effectively no files can be added to a contact message. This setting will be used in combination with CONTACTMAXFILES and CONTACTMAXTOTALFILESIZE to determine whether any (additional) files may be added or not.', 'N');
execute CreateSystemSetting('General', 'CONTACTMAXTOTALFILESIZE', '20', 'I', '20', 'N', 'N', 0, 150, '', 'This system setting defines the maximum size in MB for all documents that may be attached to a single contact message via the client application or the web portal. A value 0 means that effectively no files can be added to a contact message. This setting will be used in combination with CONTACTMAXFILES and CONTACTMAXFILESIZE to determine whether any (additional) files may be added or not.', 'N');
execute CreateSystemSetting('General', 'CONTACTPERSONEXTWEBACCESS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if the contact person dialog shows the check box "External Web Portal Access"'|| chr(10) ||''|| chr(10) ||'0 = default = no, do not show'|| chr(10) ||'1 = yes, show the field', 'N');
execute CreateSystemSetting('General', 'CONTACTPERSONMANDATORY', '0', 'I', '0', 'Y', 'N', 0, 1, '01', 'Defines if a selecting a Contact Person is mandatory on creating a contact, or data will be imported via a contact integration system.'|| chr(10) ||'0 = Contact Person is not mandatory'|| chr(10) ||'1 = Contact Person is mandatory', 'Y');
execute CreateSystemSetting('General', 'CONTACTSHOWONROUTE', 'N', 'B', 'N', 'Y', 'N', 4, 4, '', 'This setting defines the default value for the Show on Route Assistant / Show on Route Sheet flag that can be set for a contact in the Contact Manager dialog. This flag is used to indicate if a contact needs to be shown on the Route Assistant or printed Route Sheet. Possible values:'|| chr(10) ||'N = Do not show contact on Route Assistant / Route Sheet '|| chr(10) ||'Y = Do show contact on Route Assistant / Route Sheet '|| chr(10) ||'When defined as a fixed default, then the default value cannot be overruled by any user upon creation of a new contact nor may it be changed when modifying it afterwards.', 'N');
execute CreateSystemSetting('General', 'CONTACTSTATUSCONTROL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if the contact statuses are free or must be followed in a fixed order. Possible values:'|| chr(10) ||'0 = current – no controls (default)'|| chr(10) ||'1 = statuses must be followed in order and in some cases are automatically set.  Usernames are automatically set as system user', 'N');
execute CreateSystemSetting('General', 'CONTACTSTATUSES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This defines which contact statuses are visible and used in the contact manager dialog'|| chr(10) ||'0 = statuses of 1, 3, 6 are used (default)'|| chr(10) ||'1 = statuses of 1, 3, 4, 5, 6 are used '|| chr(10) ||''|| chr(10) ||'1=New'|| chr(10) ||'3=In Progress'|| chr(10) ||'4=Completed'|| chr(10) ||'5=Reviewed by Manager'|| chr(10) ||'6=Closed', 'N');
execute CreateSystemSetting('General', 'CONTAINERRECORDINGACTIVE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Effective only when container registration module is in the license of the plant. When set the containers can be used.', 'N');
execute CreateSystemSetting('General', 'CONTRACTAUTOEXTEND', '1', 'I', '1', 'N', 'N', 1, 2, '1', 'This controls the automatic extension of contracts from the Automatic contract extend process.'|| chr(10) ||''|| chr(10) ||'1 = if a contract is not set to automatically extend by a set number of months, it automatically rolls on (end date increased) by 1 month at the end date minus Term of Notice (this is often called "evergreen" as the contract will never expire)'|| chr(10) ||'2 = only contracts set to automatically extend will get extended.', 'N');
execute CreateSystemSetting('General', 'CONTRACTCUSTOMERENDDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'when adding a customer to a contract or a contract to a customer, for the customer contract end date use:'|| chr(10) ||''|| chr(10) ||'0 = use termination date'|| chr(10) ||'1 = use contract end date'|| chr(10) ||''|| chr(10) ||'NOTE: this setting is NOT used if module ContractManagement is in the license', 'N');
execute CreateSystemSetting('General', 'CONTRACTENDDATECONTROL', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Contract end date defaults to the month end date after the sign date plus duration. If changed, must be a calendar month end date.'|| chr(10) ||''|| chr(10) ||'1 = Contract end date defaults to the contract start date plus duration but is automatically changed to the first customer install date (first invoice date) plus duration when the first invoice is settled.  '|| chr(10) ||'If changed, can be any date within a month', 'N');
execute CreateSystemSetting('General', 'CONTRACTSIGNANDSTARTDATES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'this setting defines the behaviour of the start date and sign dates when creating a new contract'|| chr(10) ||'0 = Start Date and Sign date default to system date'|| chr(10) ||'1 = Start Date and Sign date default blank', 'N');
execute CreateSystemSetting('General', 'CONTRACTSTARTDATECONTROL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the contract start date is overwritten by the first customer''s install date or not'|| chr(10) ||''|| chr(10) ||'0 = default = start date is not changed'|| chr(10) ||'1 = start date is updated to the first customers install date set during the settlement process.  Only works if SETTLEMENTACTIVE = Y', 'N');
execute CreateSystemSetting('General', 'CREATEPNLINEPERDELSCHEME', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'It will be possible now to store the connection between the actual delivery and the originating delivery scheme from the delivery standards for non-straight even exchange products. This normally only done for straight-even exchange items. This data is needed for reporting purposes. Possible values:'|| chr(10) ||'N: No link between originating delivery scheme and actual delivery will be stored for on non-straight even exchange items.'|| chr(10) ||'Y: The link between the originating delivery scheme and the actual delivery will be stored for non-straight even exchange items.', 'N');
execute CreateSystemSetting('General', 'CREDITFLOWCASHAPPLY', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This controls the default / fixed value for the "Apply / Open cash application" check box on the credit flow module enabled create credit dialog.'|| chr(10) ||''|| chr(10) ||'when enabled:'|| chr(10) ||'0 = check box is not checked by default'|| chr(10) ||'1 = check box is checked by default'|| chr(10) ||''|| chr(10) ||'NOTE: this also applies to the NEGATIVEMANUALINVOICEFLOW module and popup', 'N');
execute CreateSystemSetting('General', 'CREDITFLOWHOUSEROUTE', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This controls the default / fixed value for the "House Route Only" check box on the credit flow module enabled create credit dialog.'|| chr(10) ||'when enabled:'|| chr(10) ||''|| chr(10) ||'0 = check box is not checked by default'|| chr(10) ||'1 = check box is checked by default'|| chr(10) ||''|| chr(10) ||'NOTE: this also applies to the NEGATIVEMANUALINVOICEFLOW module and popup', 'N');
execute CreateSystemSetting('General', 'CREDITFLOWROUTEASSIGN', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This controls the default / fixed value for the assign to route check box on the credit flow module enabled create credit dialog.'|| chr(10) ||'when enabled:'|| chr(10) ||''|| chr(10) ||'0 = check box is not checked by default'|| chr(10) ||'1 = check box is checked by default'|| chr(10) ||''|| chr(10) ||'NOTE: this also applies to the NEGATIVEMANUALINVOICEFLOW module and popup', 'N');
execute CreateSystemSetting('General', 'CREDITFLOWSETTLE', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This controls the default / fixed value for the "Settle Credit" check box on the credit flow module enabled create credit dialog.'|| chr(10) ||'when enabled:'|| chr(10) ||''|| chr(10) ||'0 = check box is not checked by default'|| chr(10) ||'1 = check box is checked by default'|| chr(10) ||''|| chr(10) ||'NOTE: this also applies to the NEGATIVEMANUALINVOICEFLOW module and popup', 'N');
execute CreateSystemSetting('General', 'CSVGRIDEXPORTSEPARATOR', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Separator used in csv files created when export grids.'|| chr(10) ||'1=comma'|| chr(10) ||'2=semicolon', 'N');
execute CreateSystemSetting('General', 'DAYSAFTERWICFLAGTORAG', '0', 'I', '7', 'N', 'N', 0, 99, '2', 'With module WEARERINVENTORYCONTROL garments can be flagged to be ragged to bring the circulating inventory in line with the control value.'|| chr(10) ||''|| chr(10) ||'This is the number of days after the flag start date that the scheduled process ProcessWearerInventoryControlRAG will rag these garments.', 'N');
execute CreateSystemSetting('General', 'DEBUG_LEVEL', '0', 'I', '0', 'N', 'N', 0, 6, '1', 'For generation processes, it defines how detailed the log file will be seen', 'N');
execute CreateSystemSetting('General', 'DEFAULTALLOWNOTAGREEDPL', '0', 'I', '0', 'Y', 'Y', 0, 1, '1', 'This controls the default value of Y/N for contract, price settings tab, Allow not agreed price lists check box'|| chr(10) ||'0 = No'|| chr(10) ||'1 = Yes', 'N');
execute CreateSystemSetting('General', 'DEFAULTCONTRACTDURATION', '48', 'I', '48', 'Y', 'N', 1, 99, '', 'The value of this setting determines how many months are displayed by default in the "Duration" field on the "Validity" tab of the "Contract" form when adding a new contract. However, it can still be changed to any value between 1 and 99 by the user.'|| chr(10) ||''|| chr(10) ||'This setting is only used in combination with the module "Master Account Contract Management".', 'N');
execute CreateSystemSetting('General', 'DEFAULTRENEGOTIATEPERIOD', '3', 'I', '3', 'N', 'Y', 0, 99, '', 'Representing the months before the contract end date to set the renegotiation date', 'N');
execute CreateSystemSetting('General', 'DEFAUTOBILLEXPIRATIONDATE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This setting defines the default flag, used as a default for the rental quantity adjustment detail screen in case of a sample product.  It is used to indicate whether a sample product should be charged automatically to the customer after the expiration date of the sample product has passed. '|| chr(10) ||'Possible values:'|| chr(10) ||'"N": The product will no longer appear on the invoice after the expiration date has passed. Not as a sample product, but also not as a regular product.'|| chr(10) ||'"Y": The product will no longer appear on the invoice as a sample product after the expiration date has passed. From that moment on, it will be charged at the regular price.'|| chr(10) ||''|| chr(10) ||'This setting is only of any importance when the module SAMPLE is in the license of the plant. It will be used as a trigger in a scheduled process to automatically create (negative) rental quantity adjustments for sample products that have expired. When defined as a fixed default, the user cannot overrule this setting.', 'N');
execute CreateSystemSetting('General', 'DEFLTFINALIZEDELNOTEPUTUP', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for the field - Finalize packing note to delivery note when generating put up documents - on the Delivery Note tab of the workstation form. Possible values'|| chr(10) ||'N: Packing Notes will not be automatically processed into delivery notes when generating put up documents from within the "Route Status Control" dialog.'|| chr(10) ||'Y: Packing Notes will be automatically processed into delivery notes when generating put up documents from within the "Route Status Control" dialog', 'N');
execute CreateSystemSetting('General', 'DEFSAMPLEPERIOD', '28', 'I', '28', 'Y', 'N', 0, 99999, '', 'This setting defines the default expiration period in days, used as a default for the rental quantity adjustment detail screen in case of a sample product. This period indicates the default number of days that a sample product can be used for free.'|| chr(10) ||'Possible values 0..99999.  Default value = 28.'|| chr(10) ||''|| chr(10) ||'This setting is only of any importance when the module SAMPLE is in the license of the plant. It will be used to calculate the default value for the expiration date of the sample product. When defined as a fixed default, the user cannot overrule this setting.', 'N');
execute CreateSystemSetting('General', 'DELETENOTVISITEDSTOPS', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Determines what happens with not visited stops on print route list or Mark the route as ready for transfer to PDA from Route status control or invoice generation.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Stops are not automatically deleted'|| chr(10) ||'1 = Not visited stops are always deleted'|| chr(10) ||'2 = Ask about delete not visited stops. When a route is marked as loaded in Truck Load Assistant/Manager no question is raised and stops are not deleted'|| chr(10) ||'3 = Same as 1 except moment of deletion is before generating the delivery documents direct invoice generation)'|| chr(10) ||'4 = Not visited stops are cancelled'|| chr(10) ||''|| chr(10) ||'If the customer is inactive by date and active YN = Y (so the stop is inactive), then option 3 may stop final loss charges being raised on a customer'|| chr(10) ||''|| chr(10) ||'Option 4 only cancels stops if the type is Mixed Delivery or Bring, and the stop is not linked to any Delivery Notes, Sales Notes or Straight Even Return quantities, or if the driving day is not a Garment delivery day. This option 4 is only considered as of version 9.05.02.', 'N');
execute CreateSystemSetting('General', 'DELIVERIESFORAVGDELVAR', '0', 'I', '0', 'N', 'N', 0, 99, '', 'Button for creating delivery variations for the average of the last number of deliveries.'|| chr(10) ||'0 = Button is not available'|| chr(10) ||'1 - 99 = Button is available, the valiue specifies the number of deliveries for the average calculation.', 'N');
execute CreateSystemSetting('General', 'DELIVERYDETERMINATION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Delivery date and route are determined via the delivery days. Moved routes are not taken into account.'|| chr(10) ||'1 = Delivery date and route are determined via the route schedule and route status control. Moved routes are taken into account. This method should only be used if SCANBYROUTE is set to Yes and ROUTEOBLIGATED is set to Yes, i.e. for each customer routestops are defined.', 'N');
execute CreateSystemSetting('General', 'DELIVERYSORTSEQREUSAGE', '-1', 'I', '0', 'N', 'N', -1, 999, '', 'The number of days that you have to wait before you can re-use a sort sequence value from an inactive route stop.  Check is on stop inactive date and system date.'|| chr(10) ||''|| chr(10) ||'-1 = do not show the field in ABSSolute', 'N');
execute CreateSystemSetting('General', 'DELIVERYVARREASONCODE', '0', 'I', '2', 'N', 'N', 0, 2, '', '0 = Reason code is only entered on a delivery variation in case of an adjustment reason for rental inventory change.'|| chr(10) ||'1 = Reason code can be entered on the delivery variation, not mandatory.'|| chr(10) ||'2 = Reason code must be entered on the delivery variation, mandatory.', 'N');
execute CreateSystemSetting('General', 'DELIVERYVARREFERENCE', '0', 'I', '1', 'N', 'N', 0, 1, '', '0 = Reference field on delivery variation is optional'|| chr(10) ||'1 = Reference field on delivery variation is mandatory', 'N');
execute CreateSystemSetting('General', 'DELTOINMISCARTRANSACTIONS', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This defines if customers that are not Bill To customers (so only a Del To) are allowed to be selected to have miscellaneous transactions created for them.  '|| chr(10) ||'And also controls if a Del to customer number is needed when a transaction is created for a Bill To'|| chr(10) ||'0 = Do not allow Del to customers'|| chr(10) ||'1 = Allow Del to customers and optional Del to customer ID when a transaction is created for a Bill To'|| chr(10) ||'2 = Allow Del to customers and mandatory Del to customer ID when a transaction is created for a Bill To'|| chr(10) ||''|| chr(10) ||'NOTE: if a del to customer is allowed and chosen, the miscellaneous transaction is still linked to the Bill To of the Del To', 'N');
execute CreateSystemSetting('General', 'DIRECTSALESHANDLINGCHARGE', '0.00', 'F', '0.00', 'Y', 'N', 0, 100, '', 'This systemsetting defines the default percentage for the direct sales handling charge. The default can be overwritten on the sales note.', 'N');
execute CreateSystemSetting('General', 'DIRECTUSEMAILFULLCREDITIN', 'Y', 'B', 'Y', 'Y', 'N', null, null, '1', 'Defines if fully credited direct invoices are e-mailed to customers. This refers to invoices that get the amount 0 due to adjustments being made.'|| chr(10) ||''|| chr(10) ||'So invoices where prebill is not zero and paythisamount is 0', 'N');
execute CreateSystemSetting('General', 'DIRECTUSEMAILINVOICETYPES', 'YYYY', 'S', 'YYYY', 'Y', 'N', 4, 4, 'NY', 'This string must contain Y N characters. It controls types of invoices to be sent by email.'|| chr(10) ||''|| chr(10) ||'1st character = Generated Invoices'|| chr(10) ||'2nd character = Generated additional invoices'|| chr(10) ||'3rd character = Manual Invoices (positive value)'|| chr(10) ||'4th character = Credits (regardless of credited invoice type) and negative value manual invoices', 'N');
execute CreateSystemSetting('General', 'DISPLAYSTREET3', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Setting to add 3rd address line.'|| chr(10) ||'This will be added on customer, delivery point, cost center, legal entity, stockroom and supplier.', 'N');
execute CreateSystemSetting('General', 'DRIVERSALES', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting will be used to configure whether Driver Sales functionality should be enabled or not. '|| chr(10) ||'"N" = No driver sales functionality is enabled.'|| chr(10) ||'"Y" = Driver sales functionality is enabled', 'N');
execute CreateSystemSetting('General', 'DVSORTCOUNTSEQ', '0', 'S', '1', 'Y', 'N', null, null, '0;1', 'When DVSORTCOUNTSEQ = 0, sequence is determined as it is currently done. When DVSORTCOUNTSEQ = 1, sequence is copied from Count sequence from CPL', 'N');
execute CreateSystemSetting('General', 'ENDCONTRACTWHENENDINGCUST', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This defines if the checkbox "Do not update inactive date on the contract" for updating the contract inactive date when recording a customer as lost is visible or not.'|| chr(10) ||''|| chr(10) ||'0 = current behaviour (no check box shown and inactive date on contract is automatically set)'|| chr(10) ||'1 = check box visible in recording lost business dialog - default Y'|| chr(10) ||'2 = check box visible in recording lost business dialog - default N'|| chr(10) ||''|| chr(10) ||'If this check box is not checked then the behaviour is the same as value 0.'|| chr(10) ||'If this check box is checked, then the contract inactive date will not be set.', 'N');
execute CreateSystemSetting('General', 'EXPORTCHARSET', '1', 'I', '1', 'N', 'N', 1, 11, '', 'Setting used for ascii-exports (i.e. labelprinting, bookkeeping system, edifakt, purchase order, ascii reports etc.)'|| chr(10) ||'1 = ISO-8859-1 = Latin-1 (West EU)'|| chr(10) ||'2 = ISO-8859-2 = Latin-2 (Central+East EU)'|| chr(10) ||'3 = ISO-8859-3 = Latin-3 (Turkish)'|| chr(10) ||'4 = ISO-8859-4 = Latin-4 (Scandinavia/Baltic)'|| chr(10) ||'5 = ISO-8859-5 = Cyrillic'|| chr(10) ||'6 = Windows-1250 = Extension for ISO-8859-2'|| chr(10) ||'7 = UTF-8 = Universal Alphabet '|| chr(10) ||'8 = x-mswin-936 = Simplified Chinese'|| chr(10) ||'9 = Shift-JIS = Japanese Characters'|| chr(10) ||'10 = UTF-16LE'|| chr(10) ||'11 = ISO-2022-JP (Japanese chars)', 'N');
execute CreateSystemSetting('General', 'EXPORTCHARSETSPARK', '0', 'I', '0', 'N', 'N', 0, 11, '', 'Setting used generating label files for Spark.'|| chr(10) ||'0 = Ignore, use systemsetting EXPORTCHARSET.'|| chr(10) ||'1 = ISO-8859-1 = Latin-1 (West EU)'|| chr(10) ||'2 = ISO-8859-2 = Latin-2 (Central+East EU)'|| chr(10) ||'3 = ISO-8859-3 = Latin-3 (Turkish)'|| chr(10) ||'4 = ISO-8859-4 = Latin-4 (Scandinavia/Baltic)'|| chr(10) ||'5 = ISO-8859-5 = Cyrillic'|| chr(10) ||'6 = Windows-1250 = Extension for ISO-8859-2'|| chr(10) ||'7 = UTF-8 = Universal Alphabet '|| chr(10) ||'8 = x-mswin-936 = Simplified Chinese'|| chr(10) ||'9 = Shift-JIS = Japanese Characters'|| chr(10) ||'10 = UTF-16LE'|| chr(10) ||'11 = ISO-2022-JP (Japanese chars)', 'N');
execute CreateSystemSetting('General', 'EXPORTDELIVERYSIGNATURE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Only used for module ROUTEASSISTANTPDS. This parameter is used to configure whether a DELIVERYSIGNATURE should be exported to the HHT or not.', 'N');
execute CreateSystemSetting('General', 'EXTCONSUMPPOINTSELECTION', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'This setting determines how the Consumption Point selection in the Sales Note dialog works:'|| chr(10) ||'0 = a dropdown list with all consumption points belonging to the selected department (standard functionality)'|| chr(10) ||'1 = a search control with the option to directly add new delivery points', 'N');
execute CreateSystemSetting('General', 'EXTCONTPERSONSELECTION', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'This setting determines how the Contact Person selection in the Sales Order dialog works:'|| chr(10) ||'0 = a dropdown list with all contact persons belonging to the selected customer (standard functionality)'|| chr(10) ||'1 = a search control with the option to directly add new contact persons for the selected customer'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the TRADE module is in the license.', 'N');
execute CreateSystemSetting('General', 'EXTENDEDNATIONALACCOUNT', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'This setting controls whether the national account is only used as a simple classification for grouping   customers or may be used as well to store additional (corporate) management data. As such this data will not be used in ABS however it can be used for custom reporting purposes. Possible values:'|| chr(10) ||'0 = Simple classiifcation for grouping customers (default)'|| chr(10) ||'1 = Classification for grouping customers with possibility to store management data', 'N');
execute CreateSystemSetting('General', 'HIDEGENDERFIELD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Based on the system setting, the gender field is visible or not in all areas (Wearer, RCI, WebX, RA)'|| chr(10) ||'0 - Gender field is visible everywhere'|| chr(10) ||'1 - Gender field is hidden everywhere', 'N');
execute CreateSystemSetting('General', 'IDASOILEDFLAGREQUIRED', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if adding a flag for all soiled garments scanned on the item dispense app is mandatory.'|| chr(10) ||'0 = on pressing > after scanning, the scanning screen is closed'|| chr(10) ||'1 = on pressing > after scanning, the flag all garments screen appears and choosing at least one flag is mandatory.  '|| chr(10) ||''|| chr(10) ||'NOTE: These mandatory "after scanning" flags are used as a history and not set on the unique item unless a repair flag is chosen', 'N');
execute CreateSystemSetting('General', 'INSTRUCTIONDISPLAYWEEKS', '2', 'I', '2', 'Y', 'N', 0, 9999, '', 'It represents the number of weeks when the user instructions pop up automatically when a customer is selected.', 'N');
execute CreateSystemSetting('General', 'INVOICEWRITEOFFAMOUNT', '0', 'F', '0', 'N', 'N', 0, 999, '', 'This is used in scheduled process ProcessSmallValueWriteOff.'|| chr(10) ||'It is the amount which an invoice''s remaining outstanding amount should be less than or equal to for it to be written off automatically by the scheduled process.', 'N');
execute CreateSystemSetting('General', 'LEGACY_CODE', '2', 'I', '2', 'N', 'N', 1, 3, '', 'Defines if the code used in the old system is shown on the screen, and if it is editable. Showing this field'|| chr(10) ||'is especially usefull if i.e. productcodes/numbers are reorganized and the user wants to know the code used in the past.'|| chr(10) ||'1= Don''t show.'|| chr(10) ||'2= Show, but not editable'|| chr(10) ||'3= Editable.', 'N');
execute CreateSystemSetting('General', 'LENGTHUNIT', 'KM', 'S', 'KM', 'N', 'N', null, null, 'KM;MI', 'Defines the length unit that is used on the RA as well as in the application and/or reports to calculate the distance between (GPS) locations.'|| chr(10) ||'KM = Kilometers'|| chr(10) ||'MI = Statute Miles', 'N');
execute CreateSystemSetting('General', 'LOGDESTINATION', '2', 'I', '2', 'N', 'N', 0, 2, '', 'Defines where log information for processes is stored'|| chr(10) ||'0 = write log information to database log tables only, '|| chr(10) ||'1 = write log information to ASCII files only'|| chr(10) ||'2 = write log information to both database and ASCII files.'|| chr(10) ||'Exception: some status quo processes only log to the database, irrespective of this setting.', 'N');
execute CreateSystemSetting('General', 'MAINTAINDELIVERYVARIATION', '0', 'I', '1', 'N', 'N', 0, 1, '', '0 = All delivery variations can be modified and deleted.'|| chr(10) ||'1 = Only manual delivery variations can be modified and deleted. Delivery variations that are generated cannot be modified or deleted, they must be corrected by creating a manual correction.', 'N');
execute CreateSystemSetting('General', 'MANDATORYCONTRACTFIELD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, the fields gain reason, gain competitor, estimaed weekly sales and in case of termination also loss reason and loss competitor are mandatory in the contract screen.', 'N');
execute CreateSystemSetting('General', 'MATSHIPMENTLISTRECEIVE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is only used in the module MATTRANSPORT'|| chr(10) ||'0 = Confirm all mat carry units as received (no scanning).'|| chr(10) ||'1 = Receive mat carry units one by one (scanning).'|| chr(10) ||'2 = Combined, allow the user to choose to confirm all or one by one.', 'N');
execute CreateSystemSetting('General', 'MAXROUTEDAYSTOMOVEINVOICE', '0', 'I', '0', 'N', 'N', 0, 7, '', 'This defines the maximum number of route days that an invoice for a undelivered customer can me moved forwards to from its original invoice date.  This is only used in Web X Route check in.'|| chr(10) ||''|| chr(10) ||'If 0, then no check on the number of days.'|| chr(10) ||'NOTE: this only works correctly if there are route controls in the future, it actually counts route control records not days.', 'N');
execute CreateSystemSetting('General', 'MAXWEEKSTOPURGEPERRUN', '5', 'I', '5', 'Y', 'N', 1, 99, '', 'Maximum number of weeks per purge run. Must be set to avoid running the process for a long time when a table is purged for the first time.', 'N');
execute CreateSystemSetting('General', 'MOVEDELIVEREDSTOP', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = When moving a stop only move the route status control if the packingstatus is still set to new.'|| chr(10) ||'1 = Also stops and packingnotes, delivery notes with status in progress or processed are moved.', 'N');
execute CreateSystemSetting('General', 'MULTIFACTORAUTHENTICATION', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if the Plant has Multi Factor (MFA) or Two Factor (TFA) authentication features available'|| chr(10) ||''|| chr(10) ||'If true (1) default, then the MFA / TFA options are available in SystemUser and UserRole dialogs'|| chr(10) ||''|| chr(10) ||'if false (0), then the options are hidden'|| chr(10) ||''|| chr(10) ||'NOTE'|| chr(10) ||'System user settings of TFA is for v9 client'|| chr(10) ||'User role settings of MFA is for Infinity', 'N');
execute CreateSystemSetting('General', 'MULTIPLETEMPDELSTOPSCPL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This flag indicates whether it is allowed to define more than one temporary stop period and/or one permanent (yearly) stop period in Consumption Point Logistics. Possible values:'|| chr(10) ||'''N'': Only one temporary stop period and/or permanent (yearly) stop period can be defined in Consumption Point Logistics '|| chr(10) ||'''Y'': Multiple temporary stop periods and/or permanent (yearly) stop periods may be defined in Consumption Point Logistics.', 'N');
execute CreateSystemSetting('General', 'MULTIPLETEMPRENTSTOPSCPL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This flag indicates whether it is allowed to define more than one temporary rent stop period and/or one permanent (yearly) stop period in Consumption Point Logistics. Possible values:'|| chr(10) ||'‘N’: Only one temporary rent stop period and/or permanent (yearly) stop period can be defined in Consumption Point Logistics '|| chr(10) ||'‘Y’: Multiple temporary rent stop periods and/or permanent (yearly) stop periods may be defined in Consumption Point Logistics.', 'N');
execute CreateSystemSetting('General', 'NEWCUSTOMERSTARTUPDAYS', '14', 'I', '14', 'N', 'N', 7, 9999, '', 'Defines for the Revenue Growth calculation for the Business Intelligence module for how many days after the customer startdate, transactions like add product/add wearer etc. should be considered as growth reason: New Customer. Default setting: 14 days.', 'N');
execute CreateSystemSetting('General', 'NONBUSINESSDAYCHECK', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No check'|| chr(10) ||'1 = Check on deliveries, show a warning when there are already deliveries planned for the date'|| chr(10) ||'2 = Check on deliveries, show an error when there are already deliveries planned for the date', 'N');
execute CreateSystemSetting('General', 'NOTEPREFIXLENGTH', '3', 'I', '0', 'N', 'N', 0, 6, '', 'Length of prefixes for i.e. packing note numbers, consignment note numbers, weighing ticket numbers, invoice numbers, etc.'|| chr(10) ||'Prefix typically only used in multiplant or multi business unit situations. Often the'|| chr(10) ||'business unit number is taken as prefix.'|| chr(10) ||'If 0 then no prefix is used.', 'N');
execute CreateSystemSetting('General', 'NOTINCONTRACTALLOWED', 'NNYY', 'S', 'NNYY', 'Y', 'N', 4, 4, 'NYyn', 'This string must contain Y N or y n characters. '|| chr(10) ||'Upper case = fixed (so disabled)'|| chr(10) ||'Lower case = default (so enabled)'|| chr(10) ||'It controls the values (YN) and fixed / default (enabled / disabled) for the following attributes on Contract:'|| chr(10) ||''|| chr(10) ||'Allow products not in contract - 1st character in string'|| chr(10) ||'Allow emblems not in contract - 2nd character in string'|| chr(10) ||'Allow wearer functions not in contract - 3rd character in string'|| chr(10) ||'Allow special charges not in contract - 4th character in string', 'N');
execute CreateSystemSetting('General', 'OMDSCHEDULEDFOR', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Export the Routenumber in OMD (ScheduledFor)'|| chr(10) ||'1 = Export the Employeenumber (driver) in OMD', 'N');
execute CreateSystemSetting('General', 'OMDSCHEDULEDFORMASK', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No mask for Scheduled for, number is exported as it is'|| chr(10) ||'1 = Remove the second digit, replace with a space (Sweden mask)', 'N');
execute CreateSystemSetting('General', 'ONELABELFILEPERUNIQUEITEM', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Defines if we create a separate label file for each unique item'|| chr(10) ||''|| chr(10) ||'0 = Multiple UI''s per label file is allowed'|| chr(10) ||'1 = create a separate label file per UI', 'N');
execute CreateSystemSetting('General', 'ONLYTOBEVISITEDSTOPS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting is used to allow to display in Maintain stop from route status control only to be visited stops since this extra functionality will slow down the population of the grid.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = don''t display only to be visited stops option (standard)'|| chr(10) ||'1 = display only to be visited stops option ', 'N');
execute CreateSystemSetting('General', 'ORACLETSEMAILADDRESS', '-', 'S', '', 'N', 'N', null, null, '', 'This contains the email address for sending updates to the Oracle TeleServices Platform.  Only used for module TELESERVICES', 'N');
execute CreateSystemSetting('General', 'PAYMENTWRITEOFFAMOUNT', '0', 'F', '0', 'N', 'N', 0, 999, '', 'This is used in scheduled process ProcessSmallValueWriteOff.'|| chr(10) ||'Its is the amount which a payment''s unallocated amount should be less than or equal to for it to be written off automatically by the scheduled process.', 'N');
execute CreateSystemSetting('General', 'PAYMENTWRITEOFFWEEKS', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This is used by scheduled process ProcessSmallValueWriteOff'|| chr(10) ||'It determines maximum age of a payment that can be written off by the scheduled process.'|| chr(10) ||'System date minus this value in weeks is the oldest payment date that can be written off', 'N');
execute CreateSystemSetting('General', 'PICKUPSTREVENATTEMPSTOP', '1', 'I', '1', 'Y', 'N', 1, 3, '', '1 = Pick up date is calculated based on frequency'|| chr(10) ||'2 = When in the consumption point logisitic the product has a yearly temporary delivery stop then the pick- up date is set to next week (delivery date + 7 days), else the pick-up date is calculated as for 1. '|| chr(10) ||'3 = When in the consumption point logisitic the product has a yearly temporary delivery stop then the pick-up date is determined by entering a return week. If no return week is entered then same as value 2, else (no yearly stop) the pick up date is calculated as for 1. (Available from version 7.51)', 'N');
execute CreateSystemSetting('General', 'PRICECONTROLACCESS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if prices can be modified or just added'|| chr(10) ||'This only applies to Rent, Wash, Replacement, Sales, Budget Protection, Emblem and Special charge prices and Special charge percentages'|| chr(10) ||''|| chr(10) ||'0 = default = full access'|| chr(10) ||'1 = user can only add prices and modify or delete future active prices (start date greater than system date)'|| chr(10) ||''|| chr(10) ||'Note: this is used in combination with system setting PriceControlYearsAdd for option 1'|| chr(10) ||'Note: this is specific module controlled, see analysis for details', 'N');
execute CreateSystemSetting('General', 'PRICECONTROLYEARSADD', '1', 'I', '1', 'N', 'N', 1, 50, '2', 'This is the number of years that is added onto the start date of a price added by a user in the price controls in the client and is used in combination with system setting PRICECONTROLACCESS'|| chr(10) ||''|| chr(10) ||'This only applies to Rent, Wash, Replacement, Sales, Budget Protection, Emblem and Special charges', 'N');
execute CreateSystemSetting('General', 'PRINTDELNOTEPERCONTAINER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'No = Print 1 delivery note that mentions all containers and weights'|| chr(10) ||'Yes = One note for every container', 'N');
execute CreateSystemSetting('General', 'PROCESSWINDOWCLOSETIME', '5', 'I', '0', 'N', 'N', 0, 9999, '', 'When value = 0, the process windows are automatically closed, after the process has been finished without any error or warning.'|| chr(10) ||''|| chr(10) ||'When value = n, the process windows are automatically closed after n seconds, after the process has been finished without any error or warning.', 'N');
execute CreateSystemSetting('General', 'PRODUCTCODELENGTH', '6', 'I', '6', 'N', 'N', 0, 12, '', 'Define a fixed lenght for productnumbers. '|| chr(10) ||'Leading zero''s are added by ABSSolute to the product number in order to get this length. The user should manually enter the leading zero''s when using the product code '|| chr(10) ||''|| chr(10) ||'0 means no leading zeroes needed. ', 'N');
execute CreateSystemSetting('General', 'RCIARDEBTDAYSOVERDUE', '0', 'I', '60', 'N', 'N', 0, 120, '', 'This defined the number of days overdue a customer''s debt needs to be for the stop to appear on the Web route check in ARDebt tab.'|| chr(10) ||'Which date the debt is based upon (invoice date or due date) is defined by system setting ARAGINGMETHOD '|| chr(10) ||'Default is 60 days'|| chr(10) ||'Only used if the tab is visible under module WEBRCIARDEBT', 'N');
execute CreateSystemSetting('General', 'REBILLCONTACTCATEGORY', '-', 'S', '-', 'N', 'N', null, null, '', 'This is used during the ReBill invoice adjustment process and defines the category used for the contact message generated.'|| chr(10) ||''|| chr(10) ||'Only available under a Custom module, see analysis for details', 'N');
execute CreateSystemSetting('General', 'RECALCMAXDEVIATIONPERC', '100', 'I', '100', 'N', 'N', 0, 100, '', 'This system setting is taken into account when the minimum stock levels are recalculated. If the changes are outside the percentage range set by this system setting a pre-defined person needs to be notified of this occurrence.', 'N');
execute CreateSystemSetting('General', 'RECALCULATESTDDELWEEKS', '4', 'I', '4', 'N', 'N', 2, 99, '', 'Number of weeks taken into account when recalculate standard deliveries. This system setting will be taken into account when the standard delivery lines on CPL product level are recalculated. ', 'N');
execute CreateSystemSetting('General', 'RECORDONSITEINVENTORY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When this system setting is set to ''Y'' then on-site inventory levels are recorded.'|| chr(10) ||'Note that on-site inventory is only recorded when in productlist per customer the checkbox for count soil is checked.', 'N');
execute CreateSystemSetting('General', 'RECORDTRUCKBARCODE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Used for Truck Load Assistant if the truck identification should be used.', 'N');
execute CreateSystemSetting('General', 'REDUCEFACTORA', '0', 'F', '0', 'N', 'N', 0, 10, '', 'Only used for module LINENSMOOTHENER. Factor A.', 'N');
execute CreateSystemSetting('General', 'REDUCEFACTORB', '0', 'F', '0', 'N', 'N', 0, 10, '', 'Only used for module LINENSMOOTHENER. Reduce factor B.', 'N');
execute CreateSystemSetting('General', 'REDUCEFACTORC', '0', 'F', '0', 'N', 'N', 0, 10, '', 'Only used for module LINENSMOOTHENER. Reduce factor C.', 'N');
execute CreateSystemSetting('General', 'REMOVEWEBSERVICELOG', '90', 'I', '90', 'N', 'N', 0, 999, '', 'Number of days after which the log from the web service interface is cleaned (via scheduled process)', 'N');
execute CreateSystemSetting('General', 'REPORTSERVERREACTIVATION', '15', 'I', '15', 'N', 'N', 5, 1440, '', 'This settings defines the timeframe in minutes after which a report server that was considered to be unavailable earlier is assumed to be available again (minimum value 5 minutes, maximum 24 hours).', 'N');
execute CreateSystemSetting('General', 'REPORTSERVERTIMEOUT', '500', 'I', '500', 'N', 'N', 1, 600000, '', 'This setting defines the timeframe in milliseconds in which the report server should have responded to a call from the client. If a report server has not responded within that timeframe, then the report server is considered not available anymore and will be marked as such (minimum 1 millisecond, maximum 10 minutes).', 'N');
execute CreateSystemSetting('General', 'ROSCALLOWDNSIGNATURERESET', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Via this setting, it can be controlled if it should be possible to to change the signature status of all delivery notes for a route from either signed to not signed or vice versa. When enabled, then two additional menu-options become available in the Route Close sub-menu of the Route Status Control dialog. Possible values:'|| chr(10) ||'0.  = The options are not visible (default)'|| chr(10) ||'1.  = The options are visible', 'N');
execute CreateSystemSetting('General', 'ROUTECODECHECK', '0', 'I', '0', 'N', 'N', 0, 2, '', 'this controls the Route Code field that is only visible under the ROUTESORTING module and '|| chr(10) ||'0 = free text, no checks'|| chr(10) ||'1 = free text, no checks, compulsory field'|| chr(10) ||'2 = entry is a drop down selection from the RouteCodeMaster table and the route number is defaulted and disabled from this table''s lookup value', 'N');
execute CreateSystemSetting('General', 'ROUTECONTROLCREATION', '1', 'I', '1', 'N', 'N', 1, 4, '', 'Defines what the standard method is for creating routes in the routestatuscontrol form '|| chr(10) ||'1=manual only via route control screen,'|| chr(10) ||'2=automatically when generating packing notes,'|| chr(10) ||'3=automatically when soil count is completed or when unique item is scanned in or when unique item is scanned out'|| chr(10) ||'With option 2 and 3 still manual creation is possible.'|| chr(10) ||'Option 4 is the combination of 2 and 3.', 'N');
execute CreateSystemSetting('General', 'ROUTECONTROLDOCPRINTORDER', '0', 'I', '0', 'N', 'N', 0, 1, '1', '0 = reprint order of documents is not affected'|| chr(10) ||'1 = reprint of documents is in route order, i.e. :'|| chr(10) ||'report 1, route 1'|| chr(10) ||'report 2, route 1'|| chr(10) ||'report 3, route 1'|| chr(10) ||'report 1, route 2'|| chr(10) ||'report 2, route 2'|| chr(10) ||'report 3, route 2', 'N');
execute CreateSystemSetting('General', 'ROUTECONTROLREFRESH', '5', 'I', '5', 'N', 'N', 0, 60, '', 'Setting for the automatic refresh interval for routestatuscontrol form,defined in minutes.'|| chr(10) ||'0 means no automatic refresh.', 'N');
execute CreateSystemSetting('General', 'ROUTESELECTION', 'EU', 'S', 'EU', 'N', 'N', 2, 2, 'EU;US', 'Selection on route in several reports:'|| chr(10) ||'In case EU, route selection is depending on delivery day selection. Only if delivery day is selected, specific route from that day can be selected.'|| chr(10) ||'For US route selection is independent from delivery day.', 'N');
execute CreateSystemSetting('General', 'ROUTESTATUSRESTRICTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether a check should be done on the current values of the PDA status, Packing Status and Soil Count status for a Route (Control) when trying to manually add a stop to a Route (Control) from withn the Route Status Control dialog or when trying to generate packing notes from with the Delivery Variations dialog or the Stock Count Order Status dialog. Given the combination of statuses, in some cases either a warning or an error-message should be raised. Possible values:'|| chr(10) ||'0 = Do not perform these additional validations (default)'|| chr(10) ||'1 = Do perform these validations as mentioned above', 'N');
execute CreateSystemSetting('General', 'ROUTESTOPDELIVERYPOINT', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Delivery point on route stop is optional'|| chr(10) ||'1 = Delivery point on route stop is mandatory'|| chr(10) ||'2 = Delivery point on route stop is optional, when adding a customer to a route it will default be left empty also if there is only 1 deliverypoint.'|| chr(10) ||''|| chr(10) ||'Mind: When changing the value of this system setting into 1 that all route stops must have a delivery point linked.', 'N');
execute CreateSystemSetting('General', 'SALESNOTEREADYFORINVOICIN', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = A sales note is ready for invoicing after it is completed (so there are no outstanding items on it). If it is not a direct invoice sales note, it will be invoiced on the next generated invoice.'|| chr(10) ||'1 = A sales note is ready for invoicing after it is completed but not before the requested date. So if the sales note is completed before the requested date, it will be put on hold until the requested date.'|| chr(10) ||'This setting does not affect direct invoice sales notes, these can be invoiced any time once the sales note is completed.', 'N');
execute CreateSystemSetting('General', 'SAMECOUNTRYFORMAINROUTE', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'This setting is used for the Route dialog. It controls if the mixed route that the current route should be connected to, should belong to a plant in the same country as the plant of the current route. The current route is considered a virtual route that will become part of a mixed route. Possible values:'|| chr(10) ||'Y = Only allow plants that are located in the same country as the plant of the current route'|| chr(10) ||'N = All plants may be selected'|| chr(10) ||'When defined as a fixed value, then the user is not able to select a different option at runtime. Option Y is selected as the default value.', 'N');
execute CreateSystemSetting('General', 'SCANPACKNOTEINPACKASSIST', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Scan the packing note on the PDA Packing Assistant.'|| chr(10) ||'0 = Allowed and default'|| chr(10) ||'1 = Allowed, not default'|| chr(10) ||'2 = Not allowed', 'N');
execute CreateSystemSetting('General', 'SCRUTINYHEAVYSOIL', '50', 'I', '50', 'N', 'N', 0, 100, '', 'Maximum percentage of heavy soil for Scrutiny process', 'N');
execute CreateSystemSetting('General', 'SETDFWSPLANTDEPALLDIALOGS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether it is allowed to select a different plant department than defined at workstation level in those dialogs where packing documents can be generated, Possible values:'|| chr(10) ||'0 - Do always allow to specify a plant department regardless of setting at workstation, do not take into account the setting of the workstation (default)'|| chr(10) ||'1 - Use the plant department as defined at workstation level as the default plant (packing) department when generating packing documents. When defined as a fixed default, the user is not allowed to select a different plant department. When defined as an overruleable default, the user may override the default plant department and select a different one.', 'N');
execute CreateSystemSetting('General', 'SETTINGSPASSWORDIDA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Item Dispense Application App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.', 'N');
execute CreateSystemSetting('General', 'SOILCOUNTCONFIRMCOMPLETE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether the user will be asked for confirmation when he/she tries to mark a route as completed for soil count.  Possible values:'|| chr(10) ||'     0 = Do not show any warning'|| chr(10) ||'     1 = Show warning (no is selected by default)'|| chr(10) ||'     2 = Show warning (yes is selected by default)', 'N');
execute CreateSystemSetting('General', 'SOILCOUNTDATECONTROL', 'N', 'B', 'N', 'N', 'N', null, null, 'Y;N', 'If set to Y, the date selection control shows the delivery days of the customer (like in calendar).', 'Y');
execute CreateSystemSetting('General', 'SOILCOUNTINSTREVENEXCH', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y it is possible to also do soil count from straight even exchange form. ', 'N');
execute CreateSystemSetting('General', 'SOILCOUNTROUTECHANGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Used in soil count entry via soil ticket.'|| chr(10) ||'0 = Show message Soil Ticket doesn’t belong to this route, change the route?  upon change of route. If Yes is answered then the route is changed.'|| chr(10) ||'1 = Route is automatically changed when a soil ticket or invoice or customer belonging to another route is selected.', 'N');
execute CreateSystemSetting('General', 'SOILTICKETCOPY', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Only 1 soil ticket is generated; when multiple copies are required it is printed multiple times. '|| chr(10) ||'1 = When multiple soil tickets are required, 1 soil ticket is generated and multiple linked soil bag tags are generated. '|| chr(10) ||'Used in US direct Invoicing only.', 'N');
execute CreateSystemSetting('General', 'SQRESIDUALVALUESELECTION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the SQ Residual Value process should select only those wearers that have an end date set <> 31-12-2099, or all wearers regardless of the fact whether they have and end date set or not. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Only select wearers having an end date <> 31-12-2099'|| chr(10) ||'1 = Select all wearers'|| chr(10) ||'Default value 0.', 'N');
execute CreateSystemSetting('General', 'STARTMYDAYCOMPLETECHECK', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'Used for the StartMyDay process with the WebX route check in screen'|| chr(10) ||''|| chr(10) ||'0 = no checks'|| chr(10) ||'1 = check to see if StartMyDay is complete, if not complete then show a warning on the Start My Day WebX route check in screen'|| chr(10) ||'2 = check to see if StartMyDay is complete, if not complete then show an error and hard stop on the Start My Day WebX route check in screen', 'N');
execute CreateSystemSetting('General', 'STARTMYDAYUSERCHECK', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'Used for the StartMyDay process with the WebX route check in screen'|| chr(10) ||''|| chr(10) ||'0 = No checks'|| chr(10) ||'1 = Check to see if the user who logged the StartMyDay is the same as the domain user of the currently logged in system user.  If so, then show a warning'|| chr(10) ||'2 = Check to see if the user who logged the StartMyDay is the same as the domain user of the currently logged in system user.  If so, then show an error and hard stop', 'N');
execute CreateSystemSetting('General', 'STOPNRIMPORTANT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if the stopnumber is important i.e. because it is printed on the labels for manual sorting. If so then set it  to Yes. It is shown then in the delivery tab of the customer screen. If set to No then the up and down buttons in the route stop screen are active for easy stop sequence changes. ', 'N');
execute CreateSystemSetting('General', 'STOPNRUNIQUE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Stopnumbers, excluding 0, must be unique per route. There can only be one active stop in a route with a specific number.'|| chr(10) ||'1 = Stopnumbers are not unique. There can be multiple stops with the same stopnumber in one route. There can only not exist multiple stops with the same stopnumber for the same customer.', 'N');
execute CreateSystemSetting('General', 'STOPSONROUTELIST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting is used only by route list report. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = print only stops that are delivered (standard)'|| chr(10) ||'1 = print all stops except incidentals that are not delivered.', 'N');
execute CreateSystemSetting('General', 'STREETMAXLENGTH', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Street has maximum length of 30 characters.'|| chr(10) ||'1 = Street has maximum length of 40 characters.'|| chr(10) ||''|| chr(10) ||'IMPORTANT WARNING: only put this setting to 1 when'|| chr(10) ||'All interfaces to other systems are compliant with the extended address field length, and'|| chr(10) ||'ABS Business Intelligence version is upgraded to version 1.09.10 or higher, and'|| chr(10) ||'Route Assistant app at all devices is upgraded to version 13.10 or higher', 'N');
execute CreateSystemSetting('General', 'SWITCHBOARDRESTRICTION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Value 0 means no restrictions – if the customer is not defined in BusinessUnitsPerUsergroup then the subdialogs are opened in inquiry mode.'|| chr(10) ||'Value 1 means that all customers from all business units can be seen, however if the customer that belongs to a business unit that is not available for the current user, the function buttons are disabled.'|| chr(10) ||'Value 2 means only customers can be seen that are processed or invoiced by a business unit to which the current systemuser has access.', 'N');
execute CreateSystemSetting('General', 'SYSTEMUSERSEARCH', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Serach and redisplay searchname from systemuser in the contact manager'|| chr(10) ||'1 = Search and redisplay full name from the systemuser in the contact manger', 'N');
execute CreateSystemSetting('General', 'TOUCHSCREENFRIENDLYMENU', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'Defines if the menu options in the sidebar menu of the ABSSolute client application show as bigger, touchscreen friendly, buttons. '|| chr(10) ||'This setting works in combation with the workstation setting ''Touchscreen connected'' located at the Hardware Settings tab.'|| chr(10) ||'The menu items show as bigger buttons only when both the workstation is configured as touch screen connected and this system setting is set to Y.', 'N');
execute CreateSystemSetting('General', 'USECOPIESFORAPPENDIX', 'N', 'B', 'N', 'N', 'N', null, null, '', 'USECOPIESFORAPPENDIX', 'N');
execute CreateSystemSetting('General', 'USEINTERNALPRODCUSTOMERNO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to define an internal production customer number for a consumption point. Possible values:'|| chr(10) ||'0 = Do not allow to define an internal production customer number'|| chr(10) ||'1 = Allow to define an internal production customer number', 'N');
execute CreateSystemSetting('General', 'USEWEARERFUNCTIONSUBTYPE', 'N', 'B', 'N', 'N', 'N', 0, 1, 'YN', 'This setting controls if it will be possible to define wearer function specific emblem templates. When enabled it will also become possible to define function subtypes per wearer function. In that way, one will be able to create different emblem template lines per wearer function and wearer function sub type. This implies that when defining an emblem template, one has to define whether it is a generic template accessible for all wearers, or a wearer function specific template only accessible for a limited set of wearer functions that the emblem template is linked to.'|| chr(10) ||'Possible values:'|| chr(10) ||'N = No it will not be possible to define any wearer function specific emblem templates'|| chr(10) ||'Y = Yes, it will be possible to define any wearer function specific emblem templates'|| chr(10) ||''|| chr(10) ||'It is is advised to put this setting only on Y when system setting ALLOWEMBLEM = 0', 'N');
execute CreateSystemSetting('General', 'VERTEXTAXINSTANCECODE', '-', 'S', '-', 'N', 'N', null, null, '', 'Code used for identifying which environment the BCI data came from when creating VertexTransactionLog records', 'N');
execute CreateSystemSetting('General', 'WCPCCHARGESOILWTDEFAULT', '0', 'I', '0', 'Y', 'Y', 0, 2, '', '0 = Default to not invoice soil weights'|| chr(10) ||'1 = Default to invoice soil weights'|| chr(10) ||'2 = Default to invoice Soil based on Transfer to Clean (only when module SOILTODELIVERYNOTE is in the license of the current plant)'|| chr(10) ||'3 = Yes is disabled, No is default and Soil based on Transfer to Clean is enabled (only when module SOILTODELIVERYNOTE is in the license of the current plant)', 'N');
execute CreateSystemSetting('General', 'WEEKAVGCALCPER', '10', 'I', '10', 'N', 'N', 0, 53, '', 'Number of deliveries to be used for calculating the average.', 'N');
execute CreateSystemSetting('General', 'WEIGHINGCERTIFICATION', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'This setting enables/disables the checks for Weighing Certification.'|| chr(10) ||'When this setting is set to ''Y'' and a weighing scale is attached to the workstation then the weight fields are not editable in deliverynote,bulk deliverynote and weighing touchscreen.Also the delete is not possible in weighing touchscreen.'|| chr(10) ||'When this setting is set to ''N'' then the value of system setting WEIGHINGRULES enables/disables the checks for Weighing Certification.'|| chr(10) ||''|| chr(10) ||'ABSSolute Infinity does not take this setting into account and behaves as if it is on Y. Canceling a weighing transaction will be possible.', 'N');
execute CreateSystemSetting('General', 'WEIGHINGPASSSOILCONTAINER', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'If set to N, the container_ID and containerType_ID will not be passed from the weighing process to the delivery note when the PackingNoteContainer record is created.'|| chr(10) ||''|| chr(10) ||'If set to Y then they are passed', 'N');
execute CreateSystemSetting('General', 'WEIGHINGRULES', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This system setting has effect only in combination with system setting WEIGHINGCERTIFICATION = ''N''.'|| chr(10) ||'Values: 1 = Modify electronic captured weight not allowed, only Delete. Manually always possible.'|| chr(10) ||'             2 = Modify/Delete electronic captured weight allowed. No Manual entry when scale attached.'|| chr(10) ||'ABSSolute Infinity does not take this setting into account and does not allow modifying electronic captured weights or manual entry when a weighing scale is configured.', 'N');
execute CreateSystemSetting('General', 'WEIGHINGTICKETEMPLOYEE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting is used in the Weighing Ticket TS app to clear the employee number and force the user to enter it again.'|| chr(10) ||'0 = Once entered the employee number is kept and stored for each weighing ticket that is created until it is changed or the dialog is closed.'|| chr(10) ||'1 = For each new weighing ticket that is created the employee number is cleared and needs to be entered.'|| chr(10) ||'This setting only works in combination with the workstation setting to enter the employee number set to Yes.', 'N');
execute CreateSystemSetting('General', 'WEIGHTUNIT', 'Kg', 'S', 'Kg', 'N', 'N', 2, 3, '', 'Defines the weight unit that is used in the application and in reports.'|| chr(10) ||'I.e. Kg for Europe or Lbs for US', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWCANCELWEIGHINGDELN', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'N =  cancel button in maintain delivery notes and deleting of containers for delivery notes with an origin = 8 (transfer weights)  is disabled'|| chr(10) ||'Y = no change, cancel and delete is available', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWCHANGEOUTSCANPOOLQTY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y the user may change (but only increase) the delivery quantity of scanned pool items, as soon as  there is at least one pool item scanned at this delivery note.'|| chr(10) ||'When set to N changing delivered quantity is not allowed at all as soon as there is at least one pool item scanned at this delivery note', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWCHANGEOUTSCANQTY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set the user may also decrease the delivery quantity (deletion is not possible in this case either) for those delivery note line that have at least one delivery scan record linked for non pool unique items.', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWDELIVERYBEFORECUTOFF', '0', 'I', '0', 'N', 'N', 0, 3, '', 'This setting controls whether any restrictions should be taken into account when finalizing a delivery note with respect to the cutoff dates of the customer activities. When the setting is active (<> 0), then the oldest cutoff date of the customer activities will be compared to the delivery date of the delivery note. In case the delivery date <= oldest cutoff date, then either a warning or should be shown or an error-message should be raised. In case of a warning, the user still has the possibility to finalize the delivery note. Possible values:'|| chr(10) ||'0 = Allow (default)'|| chr(10) ||'1 = allow finalize DN set for direct invoices and return an warning for DN invoiced periodical '|| chr(10) ||'2 = allow finalize DN set for direct invoices and raise error-message for DN invoiced periodical '|| chr(10) ||'3 = return an warning for direct invoices and raise error-message for DN invoiced periodical', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWNONBULKDEPDELVAR', '1', 'I', '1', 'N', 'Y', 0, 1, '', 'When a customer is setup for reallocation and the department is not the bulk department and it is not excluded from bulk delivery, then no individual packing notes can be generated for such a department.'|| chr(10) ||''|| chr(10) ||'Depending on this setting, when manually creating a delivery variation the user is either allowed to select only a bulk department or a department that is excluded from bulk delivery, or the user is allowed to select all active departments of a customer. Possible values:'|| chr(10) ||'0 - Only a bulk department or adepartment excluded from bulk may be selected (default)'|| chr(10) ||'1 - All active departments may be selected'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the customer is setup for reallocation.', 'N');
execute CreateSystemSetting('Delivery Note', 'ALLOWOVERDELIVMULTIREAD', '0', 'I', '0', 'Y', 'Y', 0, 2, '', '0 = do not use multi-read scanner'|| chr(10) ||'1 = store the multiread scan as delivered quantity (also when the quantity is higher as the packing note qt)'|| chr(10) ||'2 = do not store ANY delivery scan and give a Pop up message "Number of scans exceeds the packing note quantity"', 'N');
execute CreateSystemSetting('Delivery Note', 'ALWAYSCONSIDERDELSTOPCPL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether a temporary (or permanent) delivery stop and/or an inactive CPL-line completely stops the generation of packing note lines for a certain product. If set to 0, then it only affects the standard deliveries. In case there are any delivery variations, then they are still added to a packing note. If set to 1, then no packing note lines will be created for a certain product when there is a temporary (or permanent) delivery stop and/or an inactive CPL-line. Any existing delivery variations with a delivery date <= desired delivery date will be ignored and should be delivered later.'|| chr(10) ||'Option 2 is the same as 1 with the addition that delivery variations for soil counts and inscans that are within a period of a temporary delivery stop are set to processed immediately. This means that they will not be ordered immediately after the temporary delivery stop is over.', 'N');
execute CreateSystemSetting('Delivery Note', 'AUTOADDBUNDLESCANS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, items linked to virtual bundles linked to the delivery note will be registered as scanned out when entering the second screen.'|| chr(10) ||'This setting can only be used in combination with the module STACKLABEL and multi read stack check.', 'N');
execute CreateSystemSetting('Delivery Note', 'AUTOASSIGNLATEPACKINGNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'When US direct invoices are being generated from route status control, this system settings enables a process that runs automatically before invoice generation starts to look for an packing / delivery notes that would be under the "assign not linked" tab in maintain packing notes and link them to this route control.'|| chr(10) ||''|| chr(10) ||'0 = do not automatically link but show a warning'|| chr(10) ||'1 = silently automatically link them', 'N');
execute CreateSystemSetting('Delivery Note', 'AUTOCLEANUPDELIVERYSCANS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Delivery scans are cleaned up via the regular clean up utility.'|| chr(10) ||'1 = Delivery scans are automatically cleaned up after the delivery note is processed, except for customers where the unique items are printed on the delivery note.', 'N');
execute CreateSystemSetting('Delivery Note', 'BATCHADDTOEXISTINGNOTE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Used by delivery notes in batch and generating delivery notes via outscan dialog. When set to Yes, outscans can be added on an existing (not yet processed) delivery note, instead of creating a new one especially for these scans.', 'N');
execute CreateSystemSetting('Delivery Note', 'BATCHDELNOTEFINAL', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When creating delivery notes from out scans, if set to N then the delivery note is not processed, else it is also processed. ', 'Y');
execute CreateSystemSetting('Delivery Note', 'BOXLABELSUSAGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'System setting used to control if entered quantity on packing note box should be added to total delivered quantity or if it is already a part of total delivered quantity.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = added quantity to packing note box will be added to total delivered quantity from packing note line ( default value)'|| chr(10) ||'1 =  added quantity to packing note box is already a part of total delivered quantity from packing note line;', 'N');
execute CreateSystemSetting('Delivery Note', 'BULKONCONSIGNMENTNOTE', '1', 'I', '1', 'N', 'N', 0, 1, '', '0 = Bulk delivery notes will be put on a separate consignment note.'|| chr(10) ||'1 = Bulk delivery notes are put on the consignment note together with regular delivery notes.', 'N');
execute CreateSystemSetting('Delivery Note', 'CALCULATEDDELIVEREDQTY', '0', 'I', '0', 'N', 'N', 0, 2, '0;1;2', '0 = Normal layout – only possible to enter total delivered qty per line.'|| chr(10) ||'1 = "Counted Qty" becomes visible, and "Delivered Qty" becomes read-only. '|| chr(10) ||'It is possible to enter positive or negative values in "Counted Qty", based on the values, the system will take care of calculating the value in "Delivered Qty". '|| chr(10) ||'2 = "Counted Qty" becomes visible, but it is still possible to change the total value in the column "Delivered Qty". It is possible to enter positive or negative values in "Counted Qty", based on the values, the system will take care of calculating the value in "Delivered Qty".', 'N');
execute CreateSystemSetting('Delivery Note', 'CHECKOPENCRBINPROCESSDN', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether a check should be done on any open cleanroom batches when finalizing a delivery note. Possible values:'|| chr(10) ||'0 - do not check on open batches when finalizing a delivery note'|| chr(10) ||'1 - check on open batches when finalizing a delivery note, give user a warning'|| chr(10) ||'2 - check on open batches when finalizing a delivery note, give user an error'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module CLEANROOMBATCHES is in the license', 'N');
execute CreateSystemSetting('Delivery Note', 'CLEANROOMBOXUSAGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'System setting used to control whether a packingnote needs to be scanned or a unique item. It is not possible to scan both. Possible values:'|| chr(10) ||'0 - Scan packing note'|| chr(10) ||'1 - Scan unique items', 'N');
execute CreateSystemSetting('Delivery Note', 'CONFIRMCLEANROOMBOX', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Box number is not confirmed.'|| chr(10) ||'1 = After each scan the user must confirm the box where the item is put.', 'N');
execute CreateSystemSetting('Delivery Note', 'CONFIRMPRINTCONSNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the user will be asked for confirmation if any consignment notes should be generated and printed from within the Container Shipping Scan dialog when processing the delivery notes. Possible values:'|| chr(10) ||'0 - Consignment notes can only be generated and printed via the Print Cons. Note button. User will not be prompted upon processing delivery notes.'|| chr(10) ||'1 - When applicable, user will be prompted if consignment notes should be printed upon processing delivery notes. However, it is also possible to generate and print them separately via the Print Cons. Note button.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the LINEN module is active. If that is not the case, this setting will be ignored completely.'|| chr(10) ||'If module TRUCKLOADASSISTANT is active, then this setting will be ignored completely, and the Consignment notes are printed from Truck Load Assistant', 'N');
execute CreateSystemSetting('Delivery Note', 'CONSIGNMENTDVREFERENCE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible or not to generate and print consignment notes for a customer per customer order reference as recorded for the delivery variations. Possible values:'|| chr(10) ||'0 = Do not allow to generate a consignment note based on a customer order reference'|| chr(10) ||'1 = Do allow to generate a consignment note based on a customer order reference'|| chr(10) ||''|| chr(10) ||'This functionality can be used in combination with the load optimizer functionality because the (split) packing notes will still all have the same customer reference number', 'N');
execute CreateSystemSetting('Delivery Note', 'CONSNOTEPERBU', '0', 'I', '0', 'N', 'Y', 0, 2, '', '0 = Consignment Note is generated for customers who have activities done by the current BU or have the current BU as default BU. This could include delivery notes from other BU''s if they handle activities for the customer (standard functionality).'|| chr(10) ||'1 = Consignment Note is generated for customers who have activities done by the current BU or have the current BU as default BU, but NOT including delivery notes from other BU''s. When reprinting consignment notes, the user can ONLY reprint consignment notes of the current BU.'|| chr(10) ||'2 = Consignment Note is generated for customers who have activities done by the current BU or have the current BU as default BU, but NOT including delivery notes from other BU''s. When reprinting consignment notes, the user CAN select a range of BU''s for which to reprint the consignment notes.', 'N');
execute CreateSystemSetting('Delivery Note', 'CONTAINERTYPEUNQBRCLABEL', '0', 'S', '0', 'N', 'N', 1, 6, '', 'Defines the containertype (cart/bag/box etc.) that will be used for generating stickers with a unique barcode based on the entered number of colli.'|| chr(10) ||'Must be an exisisting containertype code.'|| chr(10) ||'0 means no unique numbers will be generated.', 'N');
execute CreateSystemSetting('Delivery Note', 'CORRECTCONSIGNMENTNOTE', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Correction ticket and original (corrected) delivery note will both be put on the consignment note.'|| chr(10) ||'1 = Correction ticket and original (corrected) delivery note will both not be put on the consignment note.'|| chr(10) ||'Only applicable for correction tickets linked to a delivery note.', 'N');
execute CreateSystemSetting('Delivery Note', 'CORRECTIONTICKETRESTRICT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1:'|| chr(10) ||'An error message is shown when a correction ticket is made for a note that is already invoiced.'|| chr(10) ||'The date of the correction ticket is copied from the original note and will be disabled,'|| chr(10) ||'A warning is shown if a correction ticket is made over a ticket that is already corrected.', 'N');
execute CreateSystemSetting('Delivery Note', 'DEFAULTVALRESTOREDELVAR', 'Y', 'B', 'N', 'Y', 'N', null, null, '', 'When DEFAULTVALRESTOREDELVAR = "N", the default value of the checkbox "Restore Delivery Variations" when cancelling packing notes is not checked. When DEFAULTVALRESTOREDELVAR = "Y", the default value of the checkbox "Restore Delivery Variations" when cancelling packing notes is checked.'|| chr(10) ||''|| chr(10) ||' ', 'N');
execute CreateSystemSetting('Delivery Note', 'DELIVERYVARIATIONSPLIT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = All delivery variations with UpdateRentQty are summed and based on the total a rental qty adjustment is created'|| chr(10) ||'1 = All positive delivery variations with UpdateRentQty are summed and based on the total a rental qty adjustment is created. All negative delivery variations are summed and only processed when there are soil counts.', 'N');
execute CreateSystemSetting('Delivery Note', 'DELNOTEALLOWNEGATIVE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Allows entry of negative quantities on delivery note. ', 'N');
execute CreateSystemSetting('Delivery Note', 'DELNOTEWARNINGLEVEL', '0', 'L', '0', 'N', 'N', 0, 9999999999, '', 'Show a warning when the delivered amount is bigger than this quantity. It is adviced to use this setting when using a keyboard scanner.', 'N');
execute CreateSystemSetting('Delivery Note', 'DNALLOWCONTZEROTARE', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting is used to control whether it is allowed to register a tare weight of 0 without confirming it explicitly as being 0 when registering the weights for a packing note. By default the tare weight as defined for the transport article itself, or the transport type (e.g. container, bag) it belongs to will be shown. Only when the default value is 0, this new setting becomes relevant. Possible values:'|| chr(10) ||'1 = User must confirm explicitly that a default value 0 is correct by entering a value 0. When pressing enter without entering any value, an error-message is shown'|| chr(10) ||'2 = A default value 0 is accepted without any problem. When pressing enter without entering a value, the default value 0 is accepted as is.'|| chr(10) ||'Note: this setting is not applicable for infinity screens like confirm packing and confirm container packing.', 'N');
execute CreateSystemSetting('Delivery Note', 'DNCONTAINERSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting is only applicable for the Container module and if the workstation is set to allow scan containers.'|| chr(10) ||'0 = Unique ID code container scan is mandatory.'|| chr(10) ||'1 = Unique ID code container scan is optional, it is also possible to select a container type without scanning an ID code or no container type.', 'N');
execute CreateSystemSetting('Delivery Note', 'DNPRODUCTGRIDSORTING', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Possible values: '|| chr(10) ||'0 = Fixed sorting of the product grid based on the following criteria'|| chr(10) ||'	PNL.PackingSequence (copied from Product.packingSequence)'|| chr(10) ||'	PNL.Product.Code'|| chr(10) ||'	Sequence number of PNL.Size as defined for the product size combination'|| chr(10) ||'1 = Free sorting of the grid.'|| chr(10) ||'Default value: 0', 'N');
execute CreateSystemSetting('Delivery Note', 'DVSHOWPRICEINFO', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When DVSHOWPRICEINFO = Y, then show ''Price'' and ''Amount'' on the delivery note and on delivery note variations. When DVSHOWPRICEINFO = N, then don''t show ''Price'' and ''Amount'' on the delivery note and on delivery note variations. ', 'N');
execute CreateSystemSetting('Delivery Note', 'EMPIDRECORDEDATPROCESSDN', '0', 'I', '0', 'N', 'N', 0, 2, '', 'this defines if an employee id is asked for during the processing of the delivery note in maintain packing and delivery notes and how it is stored.'|| chr(10) ||''|| chr(10) ||'0 = no employee number requested'|| chr(10) ||'1 = employee number entered stored against the packing note if no emplyee id is already logged'|| chr(10) ||'2 = employee number entered stored against the packing note overwritting any existing data', 'N');
execute CreateSystemSetting('Delivery Note', 'EXPFILENAMEDELNOTEINFO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Only used for module EXPORTDELNOTEINFO. This setting defines how the name of the export file should formatted. Possible values:'|| chr(10) ||'0 = <DeliveryNoteNumber>_<ProcessingBUCode>_<YYMMDD>_<HHMMSS>'|| chr(10) ||'1 = <YYMMDD>_<HHMMSSFF>_<DeliveryNoteNumber>_<ProcessingBUCode>_<MasterAccountCusto merNumber>_<DelToCustomerNumber>'|| chr(10) ||'Default value 0.', 'N');
execute CreateSystemSetting('Delivery Note', 'EXTENDEDEXTREMTRANSPLABEL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Maximum length for external remark as printed on transport label. This transport label will be printed in advance when generating packing notes. Possible values:'|| chr(10) ||'0 = Maximum 30 characters (default)'|| chr(10) ||'1 = Maximum 80 characters'|| chr(10) ||'2 = Maximum 1000 characters'|| chr(10) ||''|| chr(10) ||'Only used for module PRINTTRANSPORTLABELSINADV.', 'N');
execute CreateSystemSetting('Delivery Note', 'EXTENDEDINTREMTRANSPLABEL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Maximum length for internal remark as printed on transport label. This transport label will be printed in advance when generating packing notes. Possible values:'|| chr(10) ||'0 = Maximum 30 characters (default)'|| chr(10) ||'1 = Maximum 80 characters'|| chr(10) ||'2 = Maximum 1000 characters'|| chr(10) ||''|| chr(10) ||'Only used for module PRINTTRANSPORTLABELSINADV.', 'N');
execute CreateSystemSetting('Delivery Note', 'EXTENDEDREMARK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Remark length on packing and delivery note.'|| chr(10) ||'0 = Maximum 80 characters'|| chr(10) ||'1 = Maximum 1000 characters', 'N');
execute CreateSystemSetting('Delivery Note', 'FILLDELIVEREDAMOUNT', '0', 'I', '0', 'N', 'N', 0, 4, '', '0 = Pool items must be scanned. Therefore the deliveredamount will be set to 0 when generating packing notes (so not depending on whether they are set uniquelycoded or not for the customer). Non pool items are default filled with to be delivered.'|| chr(10) ||'1 = Pool items can be scanned or counted. When in PLPC they are set to be uniquely coded, they are scanned and the deliveredamount is set to 0. If they are not set to be uniquely coded, they are counted and the deliveredamount is set by default to the ordered amount. '|| chr(10) ||'In case the module Unique Bundles is licensed setting value 1 behaves like setting value 0.'|| chr(10) ||'2 = Both pool and non-pool are always defaulted with 0. This means all products must be confirmed to be delivered.'|| chr(10) ||'3 = Pool items are always set by default to the ordered amount, For non pool items default to ordered amount from 9.08.00(0 before).'|| chr(10) ||'4 = same as 1, except the presence of the Unique Bundles module in the license does not overrule Code Uniquely in PLPC when set to No.', 'N');
execute CreateSystemSetting('Delivery Note', 'FILLDELIVEREDAMOUNTPOOL', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Pool items must be scanned. Therefore the deliveredamount will be set to 0 when generating packing notes (so not depending on whether they are set uniquelycoded or not for the customer).'|| chr(10) ||'1 = Pool items can be scanned or counted. When in productlist per customer they are set to be uniquely coded, they are scanned and the deliveredamount is set to 0 when generating packingnotes. If they are not set to be uniquely coded, they are counted and the deliveredamount is set by default to the ordered amount when generating packingnotes.', 'Y');
execute CreateSystemSetting('Delivery Note', 'FINALIZEDNWITHOUTLINES', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Define if option print and finalize will be available on process delivery notes with lines.'|| chr(10) ||'(when there are no PackingNoteLine and no PackingNoteContainer linked to the PackingNote)'|| chr(10) ||'0 - option print and finalize is available on process delivery notes without lines or with 0 delivery lines'|| chr(10) ||'1 - option print and finalize is not available on process delivery notes without lines or with only 0 lines'|| chr(10) ||'2 - option print and finalize is not available on process delivery notes without lines or with 0 lines unless there are negative delivery variations.', 'N');
execute CreateSystemSetting('Delivery Note', 'FORCEPICKINGFROMSTOCK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether items with type-of-merchandise 3 (Disposables/Sales Only) should be explicitly issued from stock when filling in the delivered quantities for a delivery note. In that way it is made sure that the number of delivered items matches the number of items that has been taken from stock, including the creation of stock transactions. Possible values:'|| chr(10) ||'0: The user does not specify where the sales items are taken from. Stock transactions are created automatically when processing the delivery notes (Default).'|| chr(10) ||'1: The user is forced to specify how many items he actually picked from stock. Stock transactions are created immediately after the user confirms the number of picked items. ', 'N');
execute CreateSystemSetting('Delivery Note', 'LINKTOINVOICEDRC', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = When generating a delivery note via garment or batch delivery note and the route status control is already invoiced, the delivery note is disconnected and must be added manually on a route status control.'|| chr(10) ||'1 = When generating a delivery note via garment or batch delivery note and the route status control is already invoiced, the delivery note is despite linked to the route status control. It will be invoiced on the next route.', 'N');
execute CreateSystemSetting('Delivery Note', 'ORDEREDQTYEDITABLE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set it is possible to modify the ordered quantity for delivery notes not processed yet, but only from maintain delivery note form. ', 'N');
execute CreateSystemSetting('Delivery Note', 'OUTOFCIRCHISTORYTOPN', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Outofcirchistory is only linked to a delivery note when it is printed on the delivery note.'|| chr(10) ||'1 = Outofcirchistory is always linked to a delivery note'|| chr(10) ||'(Option 1 is used only for specific layouts of the delivery note).', 'N');
execute CreateSystemSetting('Delivery Note', 'OUTSCANMULTIREADDELNOTE', '0', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls how the user selects the packing note to which the scanned unique tems will be added after being scanned with the multi read out scan dialog.This is the same multi read scan dialog that is used from within the delivery note dialog via CTRL-M. The user should enter/scan the number of the packing note or the ID code of the container the packing note is packed in. Possible values:'|| chr(10) ||'0 = enter/scan the packing note number (default)'|| chr(10) ||'1 = enter/scan the id code of the container', 'N');
execute CreateSystemSetting('Delivery Note', 'OVERUNDERDELIVERYDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 0 (default) a delivery variation for overdelivery or underdelivery is created with the delivery date set to the delivery date of the packingnote + 1 day.'|| chr(10) ||'When set to 1 a delivery variation for overdelivery or underdelivery is created with the delivery date set equal to the delivery date of the packingnote.', 'N');
execute CreateSystemSetting('Delivery Note', 'PACKINGNOTEOVERVIEWDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting defines which date is selected in the packing note overview dialog.'|| chr(10) ||'0 = Production date'|| chr(10) ||'1 = Delivery date', 'N');
execute CreateSystemSetting('Delivery Note', 'PNSCANNEWPRODUCTSIZE', '0', 'I', '0', 'N', 'N', 0, 4, '', 'When a new item is scanned, checks below:'|| chr(10) ||'0 = (default) allows to scan new (not ordered) products / sizes on a packing note; no checks.'|| chr(10) ||'1 = warning if scaned qty > ordered qty (show warning, if OK, accept the scan).'|| chr(10) ||'2 = block if scanned qty > ordered qty (show warning and reject the scan).'|| chr(10) ||'3 = warning if scaned qty > to be delivered qty (show warning, if OK, accept the scan).'|| chr(10) ||'4 = block if scanned qty >  to be deliveredqty (show warning and reject the scan).', 'N');
execute CreateSystemSetting('Delivery Note', 'PNSPLITBYDVREFERENCE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether it will be possible or not to generate packing notes split per customer order reference as recorded for the delivery variations. This setting is only relevant when the PACKINGNOTEBYREFERENCE module is in the license. Possible values:'|| chr(10) ||'0 = Do not allow to generate packing notes split by customer order reference'|| chr(10) ||'1 = Do allow to generate packing notes split by customer order reference', 'N');
execute CreateSystemSetting('Delivery Note', 'PRINTDELNOTEZEROLINES', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set delivery note lines with Delivered Qty = zero will still be shown on DeliveryNote report if Ordered Qty is not zero.', 'N');
execute CreateSystemSetting('Delivery Note', 'PRINTPARKNOTE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, a button to print a park note will be available when a packing note has status ''In progress''.'|| chr(10) ||'Note: When using the Android Packing Assistant this button is available, ignoring this systemsetting.'|| chr(10) ||''|| chr(10) ||'Not used, changed to workstation setting.', 'Y');
execute CreateSystemSetting('Delivery Note', 'PROCESSDELIVERYSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = In case of a second delivery scan for the same unique item and there is no delivery note created. The outscan will be added to the next delivery note. The item is delivered 2 times.'|| chr(10) ||''|| chr(10) ||'1= In case of a second delivery scan for the same unique item and there is no delivery note created the outscan will not be added to the delivery note. The item is delivered 1 time. The old outstanding delivery scan will be removed in the background.', 'N');
execute CreateSystemSetting('Delivery Note', 'RCPRINTDELIVERYNOTES', 'Y', 'B', 'Y', 'Y', 'Y', null, null, '', 'Defines the Print Delivery Notes checkbox default selection on the Generate Direct Invoices form (EU),  when printing Del Doc from Route Status Control ', 'N');
execute CreateSystemSetting('Delivery Note', 'REASONCODEFORCEPICKING', '-', 'S', '-', 'N', 'N', 1, 6, '', 'On issue non unique sales items from Delivery note( system setting FORCEPICKINGFROMSTOCK = 1)  a stock transaction is made  with reason code set on this value when not exists one delivery variation with reason code that generate this packing note line', 'N');
execute CreateSystemSetting('Delivery Note', 'REASONCODEFREEOFCHARGE', '-', 'S', '-', 'N', 'N', null, null, '', 'This setting is used for an interface for importing delivery notes and is used to indicate the reason code for free of charge.', 'N');
execute CreateSystemSetting('Delivery Note', 'RESTRICTGENERATEPN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting manages the generation of the packing notes for the following screens: Generate packing notes, Route Status Control and Stock Count/Order Control.'|| chr(10) ||'0=Standard behavior ( at least one standard delivery was defined ).'|| chr(10) ||'1=A packing note should be generated when at least one standard delivery was defined or at least one delivery variation with origin 3 (manual), 1 (soil count), 2 (stock count) or 6 (electronic order) was found.', 'N');
execute CreateSystemSetting('Delivery Note', 'ROUNDINGMETHODSPECIALWCPC', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'Rounding method used for Weighing Category per customer of type Special:'|| chr(10) ||'0 - Standard'|| chr(10) ||'1 - Rounding method 1. The rounding alghorithm is: '|| chr(10) ||'If the special quantity is lower than 1, then it will be rounded to 1.'|| chr(10) ||'If the special quantity has the fractional part = 0.5 will remain untouch.'|| chr(10) ||'If the special quantity has the fractional part < 0.5 the quantity is rounded down to the nearest integer.'|| chr(10) ||'If the special quantity has the fractional part > 0.5 the quantity is rounded up to the nearest integer:', 'N');
execute CreateSystemSetting('Delivery Note', 'SCANEMPTYCONTAINERONDN', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Allow to scan empty containers on packingnotes only (status New or In progress)'|| chr(10) ||'1 = Allow to scan empty containers on packingnotes (status New or In progress). When Processed to a delivery note show a warning.'|| chr(10) ||'2 = Allow to scan empty containers on packingnotes (status New or In progress) and a delivery note (status Processed).', 'Y');
execute CreateSystemSetting('Delivery Note', 'SECRETEMPLOYEENUMBER', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When Y, then employee number is displayed like *. The search button for an employee is not visible. The employeenumber and employeename in the Employee-field are displayed like **|<Name of Employee>. The warning that appears when an employee has not been found, does not show the employee number.'|| chr(10) ||''|| chr(10) ||'When N, employee number is visible and search is possible.', 'N');
execute CreateSystemSetting('Delivery Note', 'SENDEMAILDELIVERYNOTE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Value 0: All send delivery notes that are not yet send '|| chr(10) ||''|| chr(10) ||'Value 1: Only send delivery notes if the delivery note is not send yet and current date is the delivery date.'|| chr(10) ||''|| chr(10) ||'Value 2: Only send delivery notes if the delivery note is not send yet and current date is the delivery date AND there is a stop with status visited in Route Status Control.', 'N');
execute CreateSystemSetting('Delivery Note', 'SRCNODELIVERY', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Systematic replacement charge is only calculated when there is a delivery for a product.'|| chr(10) ||'1 = Systematic replacement charge is also calculated when there is no delivery. Based on the setting in the PLPC the charged quantity can also be delivered.', 'N');
execute CreateSystemSetting('Delivery Note', 'STORECONTAINERSTICKERS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Number of container stickers printed is not stored.'|| chr(10) ||'1 = When number of container stickers is changed the value is stored in the number of colli.', 'N');
execute CreateSystemSetting('Delivery Note', 'UHFKNTOUTSCANINTERVAL', '0', 'I', '0', 'N', 'N', 0, 999, '', 'Defines number of hours that containers cannot be outscanned again when already outscanned before and still linked to a customer.'|| chr(10) ||'This setting can be used to prevent stray reads from containers behind a UHF portal.'|| chr(10) ||'Value zero means no check.'|| chr(10) ||'Note: this setting only applies to multiread outscanning of UHF container tags.', 'N');
execute CreateSystemSetting('Delivery Note', 'UHFOUTSCANBUNDLEPERC', '0', 'I', '0', 'N', 'N', 0, 100, '', 'With the module - UHF Complete Bundle Outscan -  the UHF outscan reading performance can be improved. This is done in case not all tags of items inside a bundle were read by the UHF antenna(s).'|| chr(10) ||'It is assumed that not scanned items in the bundle are being delivered as well. The stack check dialog should be configured to store the ID''s per bundle (set CreateBundles=Y)'|| chr(10) ||'Only when at least X % of the items in a bundle is scanned the missing ones are added.'|| chr(10) ||'This setting defines the percentage X.'|| chr(10) ||'When set to 0 this feature is turned off.', 'N');
execute CreateSystemSetting('Delivery Note', 'UHFPOOLITEMSTARTUPCALC', '2', 'I', '2', 'N', 'N', 0, 3, '', 'This setting is only applicable when setting UHFPOOLITEMSTARTUPPHASE=Y. '|| chr(10) ||'See description for that setting.'|| chr(10) ||'This setting determines what the delivered quantity should be if scanned quantity exceeds ordered quantity.'|| chr(10) ||'0 = always ordered quantity, even if scanned quantity is higher, unless ordered qty is 0'|| chr(10) ||'1 = if scanned qty is higher than ordered qty then scanned qty else ordered qty'|| chr(10) ||'2 = if scanned qty is higher than ordered qty then scanned qty else ordered qty, except when'|| chr(10) ||'ordered qty = 0 then delivered qty will be 0 too.'|| chr(10) ||'3 = always ordered quantity, even if scanned quantity is higher, also when ordered qty is 0', 'N');
execute CreateSystemSetting('Delivery Note', 'UHFPOOLITEMSTARTUPPHASE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'During the start up of a UHF tagging project not all pool items have a tag. It might take a while to tag all items. '|| chr(10) ||'When scanning pool items at the delivery note, the delivered quantity (which is 0 initially) will become the scanned quantity. However when only a minority of the items is tagged this behavior is undesirable.'|| chr(10) ||'This setting allows to scan the items that are tagged at the delivery note, while the quantity delivered will become the ordered quantity instead of the scanned quantity.'|| chr(10) ||'When tagged items should be scanned out and linked to the customer, but should not define the delivered quantity, put this setting to Y.', 'N');
execute CreateSystemSetting('Delivery Note', 'UHFSTRAYREADREDUCTION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Determines if UHF stray reads should be reduced by rejecting items that are part of a virtual bundle, for which the number of scanned items scanned has not yet reached the threshold value (defined by system setting UHFOUTSCANBUNDLEPERC). Turning this setting on implies that items in virtual bundles are outscanned  all or none.'|| chr(10) ||'0 = Off'|| chr(10) ||'1 = On', 'N');
execute CreateSystemSetting('Delivery Note', 'UPDATEPACKINGSTATUS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Packingstatus is set to completed when there is no packingnote with status new or in progress.'|| chr(10) ||'1 = Packingstatus is set to completed when there is no packingnote with status new or in progress and the invoices are generated.', 'N');
execute CreateSystemSetting('Delivery Note', 'USECUSTREFERENCEFILTER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control if it is possible to use an additional filter in the Maintain Packing and Delivery Notes dialog. When enabled, it will be possible to select only those packing/delivery notes that have been created based on delivery variations with the entered customer reference. Possible values:'|| chr(10) ||'0 = Do not enable a filter on customer reference number'|| chr(10) ||'1 = Do enable a filter on customer reference number', 'N');
execute CreateSystemSetting('Delivery Note', 'WSPRINTERNAME', '-', 'S', '-', 'N', 'N', null, null, '', 'Printer name for printing the delivery note in import of delivery notes. Only used in interface module.', 'N');
execute CreateSystemSetting('Financial Export', 'BOOKKEEPINGSYSTEM', '2', 'I', '2', 'N', 'N', 1, 15, '', 'Defines the brand of bookkeeping system or type of interface.'|| chr(10) ||'1 = Exact6 '|| chr(10) ||'2 = ABS FIBU interface'|| chr(10) ||'3 = ABS FIBU interface, with DEL-to customer in ID line'|| chr(10) ||'4 = Accpac'|| chr(10) ||'5 = Exchecker'|| chr(10) ||'6 = Aspect4'|| chr(10) ||'7 = Interface Finance Sun uses export2financesun SQL procedure'|| chr(10) ||'8 = Interface PocWin4'|| chr(10) ||'9 = Exact 6 Online'|| chr(10) ||'10 = Edifakt'|| chr(10) ||'11 = Export via (custom) stored procedure'|| chr(10) ||'12 = ABM'|| chr(10) ||'13 = Visma Mamut'|| chr(10) ||'14 = Contaplus (Fibu)'|| chr(10) ||'15 = Standard ABS REST API WS', 'N');
execute CreateSystemSetting('Financial Export', 'CREDITSQUEEZETOAR', 'Y', 'B', 'Y', 'N', 'Y', null, null, '', 'Only when this system setting is yes the credit squeeze amount is stored in AR-transactions.', 'N');
execute CreateSystemSetting('Financial Export', 'CSVCLIENTEXPFILEPREFIX', 'Client', 'S', 'Client', 'N', 'N', null, null, '', 'Filename (excluding the path) used for the client export. the date and timestamp are added to this to get the actual filename.', 'N');
execute CreateSystemSetting('Financial Export', 'EANCLEANPREFIX', '1', 'I', '1', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a weighingcategory. This digit can be set different from EANSOILPREFIX to have a different EAN number for the same weighingcategory for soil and clean weight charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EANRENTPREFIX', '1', 'I', '1', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a product. This digit can be set different from EAN-WASH/SALES/REPLACEMENT-PREFIX to have a different EAN number for the same product for the different kind of charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EANREPLACEMENTPREFIX', '3', 'I', '3', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a product. This digit can be set different from EAN-WASH/RENT/SALES-PREFIX to have a different EAN number for the same product for the different kind of charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EANSALESPREFIX', '2', 'I', '2', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a product. This digit can be set different from EAN-WASH/RENT/REPLACEMENT-PREFIX to have a different EAN number for the same product for the different kind of charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EANSOILPREFIX', '2', 'I', '2', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a weighingcategory. This digit can be set different from EANCLEANPREFIX to have a different EAN number for the same weighingcategory for soil and clean weight charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EANWASHPREFIX', '0', 'I', '0', 'N', 'N', 0, 9, '', 'For EDIFAKT Interface:'|| chr(10) ||'8th digit in the 13 digit EAN number for a product. This digit can be set different from EAN-RENT/SALES/REPLACEMENT-PREFIX to have a different EAN number for the same product for the different kind of charges.', 'N');
execute CreateSystemSetting('Financial Export', 'EDIFAKTFILENAME', 'EdiFakt', 'S', 'EdiFakt', 'N', 'N', null, null, '', 'The name of the export file that will be created.', 'N');
execute CreateSystemSetting('Financial Export', 'EDIGENERALINVNO', '0', 'I', '0', 'N', 'N', 0, 999999, '', 'Sequence number used in export to EDIFAKT, Seeburger method, as general invoice number, per export file.  '|| chr(10) ||''|| chr(10) ||'IMPORTANT: Minimum value must be set to first invoice number,'|| chr(10) ||'                       Maximum value must be set to maximum expected invoice number.'|| chr(10) ||'Just like a sequence for invoice numbers. ', 'N');
execute CreateSystemSetting('Financial Export', 'EDIINVNUMBER', '0', 'I', '0', 'N', 'N', 0, 999999, '', 'Sequence number used in export to EDIFAKT, Seeburger method, to make an invoice number per debtor.'|| chr(10) ||''|| chr(10) ||''|| chr(10) ||'IMPORTANT: Minimum value must be set to first invoice number,'|| chr(10) ||'                       Maximum value must be set to maximum expected invoice number.'|| chr(10) ||'Just like a sequence for invoice numbers. ', 'N');
execute CreateSystemSetting('Financial Export', 'EDISUPPLIERADDRESS', 'O094200005560719642:30', 'S', 'O094200005560719642:30', 'N', 'N', null, null, '', 'Only used for module EDIFAKTVOLVO and for module EDIFAKTSTD. Must be entered in format LOGICAL ADDRESS:QUALIFIER.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPACCTRANSITSTOCKFIBUHTS', '1076', 'S', '1076', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the ledger account that is used to book the stock value of items in Transit stock when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPBOOKKEEPINGDECIMALSIGN', '0', 'I', '1', 'N', 'N', 0, 1, '', 'Decimal sign that is used in the export to bookkeeping system.'|| chr(10) ||'0 = Point'|| chr(10) ||'1 = Comma'|| chr(10) ||'Note that the comma can sometimes be used as a field separator, therefore it is adviced to use the decimal point. This systemsetting is not used in all export formats.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPCOBRAMAXCLUSTER', '49', 'S', '49', 'N', 'N', null, null, '', 'Only used for module Export to Cobra. Maximum cluster selection for customers that will be exported via the scheduled process', 'N');
execute CreateSystemSetting('Financial Export', 'EXPCOBRAMINCLUSTER', '40', 'S', '40', 'N', 'N', null, null, '', 'Only used for module Export to Cobra. Minimum cluster selection for customers that will be exported via the scheduled process.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPCOMPANYFIBUHTS', '-', 'S', '-', 'N', 'N', 1, 3, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the company that should be used when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPETRAMARKETSEGMENT', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Only used for module EXPORTINVOICESETRA. This is the market segment that all customers belong to for which the finalized invoices should be exported to the ETRA Enterprise system. Must be a valid market segment code.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPFILENAMEFIBUHTS', 'EXPFIBU.HTS', 'S', 'EXPFIBU.HTS', 'N', 'Y', null, null, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the name of the file that holds the financial stock data that will be exported to the FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPFILEOPERATIONFIBUHTS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Only used for module HTSSTOCKTRANSACTIONS. This setting indicates whether the exported transactions should be appended to an existing file, or if always a new export file should be created. '|| chr(10) ||''|| chr(10) ||'This implies that when a file exists, when the export process is started the process stops because it seems that the previous file was not processed (correctly) by the external application (FIBU). The  filename and directory where the file must be located are defined via the respective system settings EXPFILENAMEFIBUHTS and EXPDIRFIBUHTS. '|| chr(10) ||'Allowed values:'|| chr(10) ||'0 – Append. When a file exists at the location as specified via the system settings above, then the transactions will be appended to the existing file. When no such file exists, then it must be created new.'|| chr(10) ||'1 – Create Only. When a file exists at the location as specified via the system settings above, then an error-message is added to the log and the export process is stopped.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPITELLACUSTOMERID', 'Pnnnnnn', 'S', 'Pnnnnnn', 'N', 'N', null, null, '', 'Only used for module EXPORTINVOICESITELLA. This is the customer ID that will be used together with the password as defined in EXPITELLAPASSWORD to identify the laundry when exporting invoices to the Itella Printing Company. '|| chr(10) ||''|| chr(10) ||'Must be set to a value other then the factory default!', 'N');
execute CreateSystemSetting('Financial Export', 'EXPITELLAPASSWORD', 'mmmm', 'S', 'mmmm', 'N', 'N', null, null, '', 'Only used for module EXPORTINVOICESITELLA. This is the password that will be used together with the customer ID as defined in EXPITELLACUSTOMERID to identify the laundry when exporting invoices to the Itella Printing Company. '|| chr(10) ||''|| chr(10) ||'Must be set to a value other then the factory default!', 'N');
execute CreateSystemSetting('Financial Export', 'EXPORTTOEDIFAKT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Option Export to EDIFakt is not available in selection screen for finalize and Print invoices.'|| chr(10) ||'1 = Option Export to EDIFakt is available in selection screen for finalize and Print invoices.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPORTVAT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'If ''Y'' then ABSSolute exports the VAT amounts, so that the bookkeeping system doesn''t have to calculate them again. If ''N'' per ledgeraccount the VAT-code is exported, so that the bookkeeping system can calculate/validate the VAT amounts. ', 'N');
execute CreateSystemSetting('Financial Export', 'EXPSTOCKDIFFACCFIBUHTS', '4190', 'S', '4190', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the ledger account that is used to book stock differences when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPSTOCKSCRAPACCFIBUHTS', '4192', 'S', '4192', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the ledger account that is used to book cost of goods scrapped when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPSUSPACCDELCOSTFIBUHTS', '1078', 'S', '1078', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the suspense ledger account that is used to book the delivery cost as charged from suppliers when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPSUSPACCSUPPLFIBUHTS', '2005', 'S', '2005', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the supplier suspense ledger account that is used to book the value of goods received from suppliers for CWS/Boco/CityMats when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'EXPTRANSITSTOCKFIBUHTS', '-', 'S', '-', 'N', 'N', 1, 10, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the transit stockroom code that should be used when exporting financial stock data to the HTS FIBU.', 'N');
execute CreateSystemSetting('Financial Export', 'FILLARTRANSACTIONDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = ARTransaction date is always filled with the invoice date'|| chr(10) ||'1 = ARTransaction date is filled depending on the invoice:'|| chr(10) ||'For in arrear invoice the end date of the invoiced period'|| chr(10) ||'For in advance invoices the start date of the in advance period'|| chr(10) ||'All other (manual, direct) invoices the invoice date.', 'N');
execute CreateSystemSetting('Financial Export', 'FILLARTRANSDATESETTLEMENT', '1', 'I', '0', 'N', 'N', 1, 2, '', 'This setting is only used for US direct invoicing with settlement.'|| chr(10) ||'1 = ARTransaction date is the driving date'|| chr(10) ||'2 = ARTransaction date is the invoice date', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPACCFILENAME', 'DEBITR.CSV', 'S', 'DEBITR.CSV', 'N', 'N', null, null, '', 'File name for export bill-to-customers (debtors) to the bookkeeping system. File will be placed in directory'|| chr(10) ||'configured in FINEXPORTDIRECTORY setting.', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPCLIENTFILENAME', 'CLIENTS.CSV', 'S', 'CLIENTS.CSV', 'N', 'N', null, null, '', 'Filename for export clients.', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPORTFILENAME', 'FMUTA6.CSV', 'S', 'FMUTA6.CSV', 'N', 'N', null, null, '', 'Name for export file of AR-transactions to the bookkeeping system.', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPORTFILENAMESUFFIX', '0', 'I', '0', 'N', 'N', 0, 2, '', 'In order to make the file unique it is possible to specify a suffix:'|| chr(10) ||'0 = No suffix'|| chr(10) ||'1 =_YYYY-MM-DD'|| chr(10) ||'2 = YYYY-MM-DD_HHMMSS'|| chr(10) ||'If a suffix is specified, the date and time are filled in reatime in the filename, just before the dot and the extension of the file.'|| chr(10) ||'Note: the suffix is only implemented for the invoice file, not for the debtor file.', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPORTLEGACYCODE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'If the system setting is set to Y then the legacy code instead of the customernumber is exported, in the export of AR-transactions to the bookkeeping system. If the setting is N then the customernumber is exported.'|| chr(10) ||'If Y but the legacy code is empty then customernumber is exported.', 'N');
execute CreateSystemSetting('Financial Export', 'FINEXPREVENUEFILENAME', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File name for reveue export', 'N');
execute CreateSystemSetting('Financial Export', 'FIXEDTEXTCLIEOP03', '-', 'S', '-', 'N', 'N', 1, 32, '', 'Only used for module CLIEOP03. This is the description that will be used to inform the debtor about the reason for creating the automatic collection transaction (Example: ABS Service Costs).'|| chr(10) ||''|| chr(10) ||'Must be filled with a value other than the factory default, otherwise no export can be created.', 'Y');
execute CreateSystemSetting('Financial Export', 'IMPORTLATECHARGEFILE', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'The directory and the name of the late charge text file exported by Oracle.', 'N');
execute CreateSystemSetting('Financial Export', 'INTERNALBUSINESSUNIT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No internal customer used'|| chr(10) ||'1 = Customer can be defined as internal business unit. This business unit code is added in the financial export.', 'N');
execute CreateSystemSetting('Financial Export', 'LAUNDRYGROUPVATNO', '-', 'S', '-', 'N', 'N', null, null, '', 'VAT number of the laundry. Used for export to EDIFAKT. ', 'N');
execute CreateSystemSetting('Financial Export', 'POCWIN4EXPORTDIRECTORY', '\POCWIN4\TRANS', 'S', '\POCWIN4\TRANS', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the customer export and invoice export will be put. Both exports will be started from within the Maintain AR Invoices dialog.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when system setting BOOKKEEPINGSYSTEM = 8 (Interface PocWIN 4)', 'N');
execute CreateSystemSetting('Financial Export', 'SENDERIDCLIEOP03', 'ABS', 'S', 'ABS', 'N', 'N', 1, 5, '', 'Only used for module CLIEOP03. This is the sender ID that will be used  to identify the laundry when creating the payment transaction file for automatic collection (Example: ABS).'|| chr(10) ||''|| chr(10) ||'Must be filled with a value other than the factory default, otherwise no export can be created.', 'Y');
execute CreateSystemSetting('Financial Export', 'TESTCODECLIEOP03', 'T', 'S', 'T', 'N', 'N', 1, 1, 'PT', 'Only used for module CLIEOP03. This setting will be usd to control whether the exported file has been sent from a testing environment or from a production environment.'|| chr(10) ||'Possible values:'|| chr(10) ||'T - The file has been sent from a test environment (default)'|| chr(10) ||'P - The file has been sent from a production environment', 'Y');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMECUSTOMER', 'VLREL', 'S', 'VLREL', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the CUSTOMER data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEMARKETSEGMNT', 'VLRSO', 'S', 'VLRSO', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the MARKETSEGMENT data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEPIECESWK', 'VLKSS2', 'S', 'VLKSS2', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the WEEKLY PIECES PROCESSED data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEPRODUCT', 'VLART', 'S', 'VLART', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the PRODUCT data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEQUANTITY', 'VLKSS', 'S', 'VLKSS', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the QUANTITIES PROCESSED data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEWEIGHT', 'VLASR', 'S', 'VLASR', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the WEIGHTS PROCESSED data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPFILENAMEWTWP', 'VLKVK', 'S', 'VLKVK', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the name of the file that holds the WEEKLY TURNOVER WEIGHTS PROCESSED data that will be exported to Virtual Laundry. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPPERIODWEEKS', '1', 'I', '1', 'N', 'N', 1, 999, '', 'Only used for module VLInterface. This flag indicates the duration of the selection period in weeks. This implies that the period starts at current week – n weeks, whereas n is defined in the current setting. ', 'N');
execute CreateSystemSetting('Financial Export', 'VLEXPUSELEGACYCODE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Only used for module VLInterface. This flag indicates whether or not any legacy codes and/or numbers will be exported to Virtual Laundry.  This concerns the legacy codes as used at customer, product, product size and weighing category level. By default,  legacy codes will be exported, to keep maximum compatibility in case of a laundry that upgrades from DOS to ABSsolute.', 'N');
execute CreateSystemSetting('Garment Recording', 'ADJUSTMAXINVENTANDMAXFREE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether also the MaxInventory and MaxFreeOfCharge should be adjusted accordingly when a unique item is changed from a chargeable item into a free-of-charge item (or vic versa) from within the Maintain Unique Item dialog.'|| chr(10) ||''|| chr(10) ||'This setting is only applicable when system setting ALLOWCHANGEFREEOFCHARGE = Y. When this setting = N, it will not be possible to change an item from chargeable into free-of-charge (or vice versa) anyway.', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWBATCHREJECTION', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0  - Do not allow batch rejection'|| chr(10) ||'1 - Allow Batch Rejection'|| chr(10) ||'2 - Allow batch rejection and clone batch', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWCHANGEFREEOFCHARGE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set, the user is allowed to make a unique item free of charge or not free of charge in maintain unique items.', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWCUSTLOCKERSHARING', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Allow  bank and locker for several customers.'|| chr(10) ||'0 = not allowed bank and locker for several customers (default value)'|| chr(10) ||'1 = allow bank and locker for several customers', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWEDCIRCDECREASEPERC', '10', 'I', '10', 'Y', 'N', 0, 100, '', 'This percentage is used by the report Inventory Decrease Analysis.'|| chr(10) ||'All customers having a decrease in their circulating inventory bigger or equal to this percentage will be shown in the report. ', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWFMWEARERFUNCTION', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No finishing method on wearer function'|| chr(10) ||'1 = Finishing method is optional on wearer function'|| chr(10) ||'2 = Finishing method is mandatory on wearer function', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWGARMNTQTYCHANGEINRCI', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'this defines if the quantity and changes fields in Web Route Check In, Wearer Maintenance (previously Orders) tab can be edited.'|| chr(10) ||''|| chr(10) ||'0 = cannot be edited'|| chr(10) ||'1 = can be edited', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWISSUECONVPRODUCT', '1', 'I', '1', 'N', 'N', 0, 2, '', 'Used in issue screens for garments. The setting controls whether it must be checked if the selected product is still active or already converted/about to be converted. Depending on the value of the setting, either no check will be done, or a check will be done and a warning will be raised, but the user can still issue the items, or an error-rmessage will be raised and it will not be possible to issue any items for the converted product. Possible values'|| chr(10) ||'0 - Do not check if the product is converted/about to be converted'|| chr(10) ||'1 - Do check, but only give a warning when product is no longer active'|| chr(10) ||'2 - Do check, but do not allow issue when product is no longer active (converted) ', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWISSUEMORETHANREQUEST', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'used on issue screens. If set to Y it is possible to issue more items than requested. Default = N.', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWREPLACEFREEINVENTORY', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'This setting is used to indicate whether it is allowed or not to replace a free inventory item with another free inventory item. When defined as a fixed default, the user cannot override it. Possible values:'|| chr(10) ||'0 = Free inventory items may only be replaced by chargeable items (default)'|| chr(10) ||'1 = Free inventory items may only be replaced by free inventory items'|| chr(10) ||''|| chr(10) ||'This value is only relevant when system setting ALLOWFREEINVENTORY = Y and it will be used in combination with system setting ALLOWREPLACEFREEINVENTORY.', 'N');
execute CreateSystemSetting('Garment Recording', 'ALLOWSEASONWEARERFUNCTION', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No season on wearer function'|| chr(10) ||'1 = Season can be defined on wearer function if product is seasonal (optional)'|| chr(10) ||'2 = Season must be defined on wearer function if product is seasonal (mandatory)', 'N');
execute CreateSystemSetting('Garment Recording', 'ALTERNATESORTING', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Setting applicable for sorting system interface only.'|| chr(10) ||'Defines if sorting is done in pairs/sets of products:'|| chr(10) ||'(jacket/pant/jacket/pant instead of jacket/jacket/pant/pant).'|| chr(10) ||'Alternation is based on Packing Sequence of product.'|| chr(10) ||'This is a default setting, can be defined per customer.'|| chr(10) ||'It depends on the sorting system supplier, if it is supported or not.'|| chr(10) ||'Default value is N.', 'N');
execute CreateSystemSetting('Garment Recording', 'AUTOREPLACEMINIMUM', '0', 'I', '0', 'N', 'N', 0, 9999, '', 'The minimum number of items that are marked for replacement. Used in combination with AUTOREPLACEPERCENTAGE.', 'N');
execute CreateSystemSetting('Garment Recording', 'AUTOREPLACEPERCENTAGE', '0', 'I', '0', 'N', 'N', 0, 100, '', 'The maximum percentage of the to be replaced items that can be marked for replacement. When set to 0 there is no check done on the maximum percentage.', 'N');
execute CreateSystemSetting('Garment Recording', 'CHECKINTERNALSORTINGPLANT', '1', 'I', '1', 'Y', 'N', 0, 1, '01', 'Check internal sorting plant, default 1 means do not check, 0 means check.'|| chr(10) ||'If systemsetting CHECKINTERNALSORTINGPLANT = 0 then an additional check will be performed. '|| chr(10) ||'Then the system will check via customer activitities for the activity of the product group the internal businessunit that is linked to the customer activitiy and then the plant that is linked to it, that plant must then be the same as the plant code that is used in the parameter of the getgarmantdata metricon.', 'N');
execute CreateSystemSetting('Garment Recording', 'COMBINELOCKERGD', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = It is only allowed to have garment dispenser or cupboard locker functionlaity configured per customer'|| chr(10) ||'1 = Both garment dispenser and cupboard locker functionality can be activated per customer.', 'N');
execute CreateSystemSetting('Garment Recording', 'COMPCHECKNONUNIQUE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Defines whether the standard completeness check dialog should show non-unique products or not (counted quantities IN <> OUT).'|| chr(10) ||'Possible values: '|| chr(10) ||'0: Show non-unique products in completeness check dialog(default value)'|| chr(10) ||'1: Do not show non-unique products in completeness check dialog'|| chr(10) ||'2: Do not show non-unique products in completeness check dialog but show unique pool products scanned in. (option 2 available from release 9.01.01)'|| chr(10) ||'Difference between option 1 and 2 is that option 2 (available from v. 09.01.00) shows scanned in based on new soilcountsubtype.', 'N');
execute CreateSystemSetting('Garment Recording', 'CUSTOMEROWNEDEDITABLE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set the user is allowed to make a unique item customer owned if it is laundry owned and vice versa in the maintain unique item dialog (except when the item is on stock).', 'N');
execute CreateSystemSetting('Garment Recording', 'CUSTOMERRELATEDEDITABLE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether the user is allowed to change a unique item ON STOCK from customer related to non-customer related (but not vice versa) in the maintain unique item dialog. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not allow to change the unique item from customer-related stock to general stock'|| chr(10) ||'1 - Do allow to change the unique item from customer-related stock to general stock', 'N');
execute CreateSystemSetting('Garment Recording', 'DEFAULTFLAGRETURNITEMS', '1', 'I', '1', 'Y', 'N', 1, 6, '', 'This setting will be used to control which option should be selected by default to flag the return items when manually decreasing the Max Inventory for a wearer inventory. Possible values:'|| chr(10) ||'1 = Return items that first show up in laundry'|| chr(10) ||'2 = Return oldest items'|| chr(10) ||'3 = Return newest items '|| chr(10) ||'4 = Return most washed items'|| chr(10) ||'5 = Return least washed items'|| chr(10) ||'6 = Return items that have the oldest (last) scan date'|| chr(10) ||'Default value 1, which means that by default nothing changes when compared to the current implementation', 'N');
execute CreateSystemSetting('Garment Recording', 'DEFAULTUSERDEFINEDEMBLEM', '1', 'I', '1', 'Y', 'N', 1, 4, '', 'This setting controls which emblem type option will be selected by default when creating a user defined emblem. Possible values:'|| chr(10) ||'1 - Company'|| chr(10) ||'2 - Name'|| chr(10) ||'3 - Other/Not Defined'|| chr(10) ||'4 - Title'|| chr(10) ||'When defined as a fixed value, the user cannot select another option then the one that is defined as the default.', 'N');
execute CreateSystemSetting('Garment Recording', 'DEFBYPASSCHECKPOINTFLAG', '-', 'S', '-', 'N', 'N', 1, 6, '', 'This attribute is used to define which flag should be used to control whether a unique item should bypass the checkpoint station when using an automatic sorting system. Should be a garment/wearer type flag.'|| chr(10) ||''|| chr(10) ||'This attribute will be used in combination with system setting NOOFWASHESNOCHECKPOINT.', 'N');
execute CreateSystemSetting('Garment Recording', 'DEFINEEMBLEMSTYLECODE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if it will be possible to define an emblem style code when setting up a user defined emblem within an emblem template. Possible values:'|| chr(10) ||'0 - Do not allow the user to define a style code'|| chr(10) ||'1 - Do force the user to select a style code', 'N');
execute CreateSystemSetting('Garment Recording', 'DEPOSITSTOCKINCC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines whether the standard completeness check dialog and the dialog  Completeness Check Scans And Counts should show unique items with stay 37 = Deposit stock.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 : Show unique items with stay 37 = Deposit stock (Default value)'|| chr(10) ||'1: Do not show unique items with stay 37 = Deposit stock', 'N');
execute CreateSystemSetting('Garment Recording', 'EMBLEMCOLORANDSIZEFILTER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if the standard color definition is used when defining user-defined emblems, or if some additional attributes can be set that allow the user to select emblem colors via an extended filter in a color search control. In addition to that an additional attribute on emblem size level can be set to filter on regular emblem sizes or custom emblem sizes. Possible values:'|| chr(10) ||'0 - Standard emblem color/size definition and filter'|| chr(10) ||'1 - Extended emblem color/size definition and filter', 'N');
execute CreateSystemSetting('Garment Recording', 'EMBLEMFONTPLACEMENTOBL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the font and placement attributes are obligated when setting up an emblem definition for a user defined emblem. Possible values:'|| chr(10) ||'0 - Both fields are optional (default)'|| chr(10) ||'1 - Both fields are obligated', 'N');
execute CreateSystemSetting('Garment Recording', 'EMBLEMSONSALESNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = The price of emblems is included in the price of the product. So the emblems are not invoiced separately.'|| chr(10) ||'1 = a separate price is charged for emblems on a sales note.', 'N');
execute CreateSystemSetting('Garment Recording', 'EMBLEMUNIQUEPLACEMENT', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0- More emblems are allowed for the same placement'|| chr(10) ||'1. Only one emblem per placement', 'N');
execute CreateSystemSetting('Garment Recording', 'EXPORTSECONDARYIDCODE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Depending on this the export to the garment dispenser will export primaryid (setting = N) or secondaryid (setting = Y)'|| chr(10) ||'This setting does not work with Standard or WnC interface.', 'N');
execute CreateSystemSetting('Garment Recording', 'FORECASTCORRECTION', '100', 'F', '100', 'N', 'N', 0, 999, '', 'This value is used in module Sortingsystem, using sorting with forecast and without inscan. The forecast is calculated: number of items in circ * Percentage defined per stop * Forecastcorrection (percentage).', 'N');
execute CreateSystemSetting('Garment Recording', 'FREEZERESVALUEQUITWEARER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y the residual value for unique items in circulation of a wearer that has a date inactive smaller than current date is not calculated anymore. '|| chr(10) ||'When set to N the residual value for quit wearers (wearer date inactive <> 31-dec-2099) is always calculated.', 'N');
execute CreateSystemSetting('Garment Recording', 'GARMENTSDISPENSERFIXCODE', '-1', 'S', '-1', 'N', 'N', 1, 2, '', 'This system setting manage the Convoyer value for Kannegiesser Garments dispenser and only for the wearer export file for transaction 400.'|| chr(10) ||'If value is  -1(default value) then the dispenser number from dispenser code defined on wearer level is exported.'|| chr(10) ||'Otherwise the value from this system setting is exported.', 'N');
execute CreateSystemSetting('Garment Recording', 'GARMENT_SER', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File directory for the ascii file GARMENT.SER'|| chr(10) ||'For the import procedure that will import the file called Import_Garment_SER'|| chr(10) ||'Remark: this directory must exist on the Oracle server and Oracle user must have the rights to access this direcetory. Also Oracle directories can be used as a setting value.', 'N');
execute CreateSystemSetting('Garment Recording', 'GARMENT_SER_PROCESSED', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File directory for the ascii file GARMENT.SER once it has been processed it will be moved here.'|| chr(10) ||'Related to the system setting GARMENT_SER', 'N');
execute CreateSystemSetting('Garment Recording', 'GDSUBFOLDERSTRUCTURE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether to use sub folders per garment dispenser interface type or not. As long as only one single type of interface is used for a customer, there is no need to have separate folders per interface type. Possible values:'|| chr(10) ||'0 = Do not use subfolders'|| chr(10) ||'1 = Do use subfolders for different interface types (brands of Garment Dispensers)', 'N');
execute CreateSystemSetting('Garment Recording', 'GUARANTEEDMINDELDAYS', '0', 'I', '0', 'N', 'N', 0, 9, '', 'Only used for the module Guaranteed Minimum delivery. Define the number of days for which a delivery lot is created in advance.', 'N');
execute CreateSystemSetting('Garment Recording', 'INCLUDEINSCANPOOLINCC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if unique pool items that have been scanned in for a cleanroom batch should be included in the scanned in items in the Completeness check dialog. Possible values:'|| chr(10) ||'0 = Exclude unique pool items scanned in for a cleanroom batch (default 0)'|| chr(10) ||'1 = Include unique pool items scanned in for a cleanroom batch', 'N');
execute CreateSystemSetting('Garment Recording', 'ISSUEREFERENCEWEEK', '1', 'I', '1', 'N', 'N', 1, 53, '', 'Reference week for calculating the "encrypted" issue reference week of the garment. This issue reference week can be printed on the label to "hide" the real issue date for the customer. The reference week is determined as number of weeks between ISSUEREFERENCEYEAR/WEEK from systemsettings and the issue week. ', 'N');
execute CreateSystemSetting('Garment Recording', 'ISSUEREFERENCEYEAR', '2000', 'I', '2000', 'N', 'N', 1800, 2099, '', 'Reference year for calculating the "encrypted" issue reference week of the garment. This issue reference week can be printed on the label to "hide" the real issue date for the customer. The reference week is determined as number of weeks between ISSUEREFERENCEYEAR/WEEK from systemsettings and the issue week. ', 'N');
execute CreateSystemSetting('Garment Recording', 'LABELLAYOUTCHOICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes then allow the user selecting another label layout than the default one, when printing labels in issue screens.'|| chr(10) ||'If set to No, the label layouts are fixed (as defined in customer screen). '|| chr(10) ||'This setting is valid for both code labels as well as name labels.'|| chr(10) ||''|| chr(10) ||'Please notice that the printed labels will all be invoiced against the customers price for his default label layout (the price will be the same, if multiple different layouts are printed).', 'N');
execute CreateSystemSetting('Garment Recording', 'LOCKERSORTINGGROUPS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Locker sort groups are not used'|| chr(10) ||'1 = Locker sort groups are defined for the use in the sorting system.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAKECOGITEMADDLOCKER', '0', 'I', '0', 'Y', 'N', 0, 1, '01', 'Used for showing Locker information in Make Unique Customer Owned dialog'|| chr(10) ||'0 - Locker information not shown'|| chr(10) ||'1 - Locker information shown', 'N');
execute CreateSystemSetting('Garment Recording', 'MARKLASTSCANDATE', '0', 'I', '0', 'N', 'N', 0, 999, '', 'If this value <> 0 then this value is the number of days after which the last scandate is marked in red. For instance if set to 90, then last scandate will be marked in red if the date is 90 days or longer in the past.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXGARMENTBATCHSORT', '120', 'I', '120', 'N', 'N', 0, 999, '', 'Only used for the module GARMENTBATCHSORT. Maximum number of boxes reserved in a batch', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXMANUALSORTBATCHSIZE', '64', 'I', '64', 'N', 'N', 0, 128, '', 'Only used for modules SORTINGSUPPORT and GUARANTEEDMINIMUMDELIVERY. Define the maximum size of a sorting batch.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXSORTLENGTHCUSTOMER', '12', 'I', '12', 'N', 'N', 4, 12, '', 'Defines the length of the customer# element in the sort string passed by the sorting system interface to the automatic garment sorting system.'|| chr(10) ||'Usage:'|| chr(10) ||'Only adjust this setting in case it is needed to reduce the total length of the sort string, to prevent that it exceeds the limit defined by setting SORTSTRINGLENGTH'|| chr(10) ||'Warning:'|| chr(10) ||'Adjusting this setting can lead to wrong sorting order of routes that are only partly loaded into the sorting system at the moment of adjusting this setting. Completely finish loading on hand routes before changing.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXSORTLENGTHDELPOINT', '12', 'I', '12', 'N', 'N', 2, 12, '', 'Defines the length of the delivery point# element in the sort string passed by the sorting system interface to the automatic garment sorting system.'|| chr(10) ||'Usage:'|| chr(10) ||'Only adjust this setting in case it is needed to reduce the total length of the sort string, to prevent that it exceeds the limit defined by setting SORTSTRINGLENGTH'|| chr(10) ||'Warning:'|| chr(10) ||'Adjusting this setting can lead to wrong sorting order of routes that are only partly loaded into the sorting system at the moment of adjusting this setting. Completely finish loading on hand routes before changing.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXSORTLENGTHSTOP', '6', 'I', '6', 'N', 'N', 2, 6, '', 'Defines the length of the stop# element in the sort string passed by the sorting system interface to the automatic garment sorting system.'|| chr(10) ||'Usage:'|| chr(10) ||'Only adjust this setting in case it is needed to reduce the total length of the sort string, to prevent that it exceeds the limit defined by setting SORTSTRINGLENGTH'|| chr(10) ||'Warning:'|| chr(10) ||'Adjusting this setting can lead to wrong sorting order of routes that are only partly loaded into the sorting system at the moment of adjusting this setting. Completely finish loading on hand routes before changing.', 'N');
execute CreateSystemSetting('Garment Recording', 'MAXSORTLENGTHWEARERNR', '12', 'I', '12', 'N', 'N', 4, 12, '', 'Defines the length of the wearer# element in the sort string passed by the sorting system interface to the automatic garment sorting system.'|| chr(10) ||'Usage:'|| chr(10) ||'Only adjust this setting in case it is needed to reduce the total length of the sort string, to prevent that it exceeds the limit defined by setting SORTSTRINGLENGTH'|| chr(10) ||'Warning:'|| chr(10) ||'Adjusting this setting can lead to wrong sorting order of routes that are only partly loaded into the sorting system at the moment of adjusting this setting. Completely finish loading on hand routes before changing.', 'N');
execute CreateSystemSetting('Garment Recording', 'MOVEGARMENTPERIODDAY', '5', 'I', '5', 'Y', 'N', 1, 999, '', 'It represents the number of days the garment stays moved to the new customer / wearer. ', 'N');
execute CreateSystemSetting('Garment Recording', 'NODAYSUSERINSTRSCANDCOUNT', '0', 'I', '0', 'N', 'N', 0, 365, '', 'Manage if a scanned ID code should be used in Completeness scan and count in customer tab for a quick fill of details. The ID code will be validated only if the planned out date for scanned id code is less than system date plus this number of days.'|| chr(10) ||'Value 0 means no check.', 'N');
execute CreateSystemSetting('Garment Recording', 'NOOFWASHESNOCHECKPOINT', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This setting is used to control whether a unique item should be inspected at the checkpoint station or not when it has been washed/processed less times than defined at PLPC level, Product level or the current setting. Possible values:'|| chr(10) ||'0 - Do not check if the checkpoint may be bypassed during the automatic sort (default)'|| chr(10) ||'1..999 - Do verify if the checkpoint may be bypassed during the automatic sort.'|| chr(10) ||''|| chr(10) ||'Will be used in combination with system setting DEFBYPASSCHECKPOINTFLAG', 'N');
execute CreateSystemSetting('Garment Recording', 'NUMBEROFDAYSFORPREWASH', '1', 'I', '1', 'N', 'N', 0, 14, '', 'This setting will be used to configure how many days (to do the pre-wash) should be added to the total preparation time when calculating the requested delivery date for  a work order.', 'N');
execute CreateSystemSetting('Garment Recording', 'OUTOFCIRCACTION', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0 = No action'|| chr(10) ||'1 = Decrease max inventory'|| chr(10) ||'2 = Create work order for replacement'|| chr(10) ||'Default action when taking items out of circulation (return to stock or rag).', 'N');
execute CreateSystemSetting('Garment Recording', 'OUTSCANSORTBATCHCOLOR', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Use the sorting colot as background color.'|| chr(10) ||'1 = Also show the SortingColor Number and use the as background color.', 'N');
execute CreateSystemSetting('Garment Recording', 'PURGEINTERNALVALUEHISTORY', '0', 'I', '0', 'N', 'N', 0, 53, '', '0=no purging, history is kept and should be removed manually'|| chr(10) ||'>0=only delete information that is older then the number of weeks specified with this setting.', 'N');
execute CreateSystemSetting('Garment Recording', 'RAGINBATCHASSIGN', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Items with status Assigned are (default) not included in rag in batch'|| chr(10) ||'1 = Items with status Assigned are (default) included in rag in batch', 'N');
execute CreateSystemSetting('Garment Recording', 'RAGINBATCHEXTRALOG', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No extra log'|| chr(10) ||'1 = Extra log, showing items that are not ragged.', 'N');
execute CreateSystemSetting('Garment Recording', 'RAGINBATCHNOTDELIVERED', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No restriction on items that have been scanned out but not delivered yet'|| chr(10) ||'1 = Items that have been scanned out but not delivered are not ragged', 'N');
execute CreateSystemSetting('Garment Recording', 'RAGINBATCHRETURNED', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Returned items are not included in Rag in Batch'|| chr(10) ||'1 = Returned items are included in Rag in Batch', 'N');
execute CreateSystemSetting('Garment Recording', 'RAGINBATCHSTAY', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = No selection on stay, all stays are included'|| chr(10) ||'1 = Selection on stay, default the stays that are marked to be included in rag in batch are selected', 'N');
execute CreateSystemSetting('Garment Recording', 'REASONCODEFREEINVENTORY', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code to be filled in by default when manually creating a replacement workorder for a unique item that was marked as free of charge item.'|| chr(10) ||''|| chr(10) ||'This value is only relevant when system setting ALLOWFREEINVENTORY = Y', 'N');
execute CreateSystemSetting('Garment Recording', 'REPAIRFRONTBACKCOLOR', '0', 'I', '0', 'N', 'N', 0, 1, '', '0=Distinction between front and back repairs with colors active repairs at front are colored red, repairs at back are colored blue. Default for backward compatibility'|| chr(10) ||''|| chr(10) ||'1=No distinction between front and back repairs by means of colors', 'N');
execute CreateSystemSetting('Garment Recording', 'REPLACEMENTREASONCODEWOW', '-', 'S', '-', 'Y', 'N', 1, 6, '', 'Default value for use in the Work Order Wizard. This is only used when a replacement work order is created, and when started from the ''Maintain Unique Items'' dialog.', 'N');
execute CreateSystemSetting('Garment Recording', 'REPLACEMENTWORKORDER', '1', 'I', '1', 'N', 'N', 1, 4, '', 'In case of replacement / renewing of unique item(s):'|| chr(10) ||'1 = If a work order exists for the wearer, with the same reason code and status ''New'' then add to this work order, else create a new work order.'|| chr(10) ||'2 = Always create a new work order.'|| chr(10) ||'3 = If a work order exists for the wearer, with the same reason code and status ''New''  that has not been printed yet, then add to this work order, else create a new work order.'|| chr(10) ||'4 = If a work order exists for the wearer and the same wearer inventory line, with the same reason code and status ''New''  that has not been printed yet, then add to this work order, else create a new work order.'|| chr(10) ||''|| chr(10) ||'Note: in case of product/size change always a new work order is created. Option 4 is supported as of v9.03.03'|| chr(10) ||''|| chr(10) ||'Note: Ignore this system setting for Work Orders with status Waiting for Approval', 'N');
execute CreateSystemSetting('Garment Recording', 'REPLACESMARTBARCODEOPTION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This controls what happens if you are scanning a smart barcode for replacement and there are no non unique items left to replace.  So there is an additional item for the wearer inventory over the current Max quantity.'|| chr(10) ||''|| chr(10) ||'0 = increase circ only (default)'|| chr(10) ||'1 = increase circ and max'|| chr(10) ||'2 = hard stop'|| chr(10) ||''|| chr(10) ||'only relevant if module SMARTBARCODES is in the license', 'N');
execute CreateSystemSetting('Garment Recording', 'ROUTERETURNSUNEXPECTED', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This controls if unexpected garments (so ones not scanned as returned on the route assistant) are allowed to bs scanned as returned in the route returns dialog'|| chr(10) ||''|| chr(10) ||'0 = default = Y'|| chr(10) ||'1 = No, so if there is no 804 route transaction not processed for this ID code - then the scan is rejected', 'N');
execute CreateSystemSetting('Garment Recording', 'SCANANDCOUNTUSERINSTR', '-', 'S', '-', 'N', 'N', null, null, '', 'Define the general user instruction code that is used in Completeness scan and count in Customer tab when an ID code was scanned and planned out date is in advance date  and it is more days in advance compare with system date than the number of days as defined in the system setting NODAYSUSERINSTRSCANDCOUNT.', 'N');
execute CreateSystemSetting('Garment Recording', 'SCANSANDCOUNTSEXTENDED', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'Defines if the extra tab-page F12 Routes per date is visible in dialog Completeness Check Scans And Counts.'|| chr(10) ||'Possible values: '|| chr(10) ||'0:  No extra tab showing routes per date ( default value)'|| chr(10) ||'1:  Extra tab showing routes per date', 'N');
execute CreateSystemSetting('Garment Recording', 'SCANSANDCOUNTSOVERDEL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the delivery note process initiated from the dialog Completeness Check Scans And Counts should created delivery variations for over deliveries for counting products.'|| chr(10) ||'Possible values: '|| chr(10) ||'0: Do not correct over deliveries for count products (default value)'|| chr(10) ||'1:  Correct over deliveries for count products', 'N');
execute CreateSystemSetting('Garment Recording', 'SCANSANDCOUNTSSHORTAGES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the delivery note process initiated from the dialog Completeness Check Scans And Counts should created delivery variations for shortages for counting products.'|| chr(10) ||'Possible values: '|| chr(10) ||'0: Do not correct shortages for count products ( default value)'|| chr(10) ||'1:  Correct shortages for count products', 'N');
execute CreateSystemSetting('Garment Recording', 'SECONDARYIDCODE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Depending on the systemsetting SECONDARYIDCODE a check is done on the secondary ID code on issue garments. This setting has the following options:'|| chr(10) ||'0 = No check is done on secondary ID code'|| chr(10) ||'1 = Secondary ID code is mandatory for wearers that are using a garment dispenser'|| chr(10) ||'2 = Secondary ID code is mandatory for all wearers.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTBATCHCONTROLREFRESH', '5', 'I', '5', 'N', 'N', 0, 60, '', 'Refresh rate in minutes for SortBatchControl dialog. 0 means no automatic refresh.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTBATCHINTERFACE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Standard sort batch interface via stored procedures'|| chr(10) ||'1 = Interface via ASCII file'|| chr(10) ||'Note: this setting is only applicable for sortingsysteminterface using sort batches.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTBATCHMERGING', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Used when merging batches in Sort Batch Control dialog.'|| chr(10) ||'0 = Old functionality, it is not allowed to merge batches with different dates'|| chr(10) ||'1 = Allow merging batches with different dates', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTINGDAYSRECALCDELDATE', '0', 'I', '0', 'N', 'Y', -1, 99, '', 'This setting is used when processing inscans in the sorting system interface. '|| chr(10) ||'In case a garment receives an inscan transaction from the sorting system and the current stay is In Laundry (which means the garment is already scanned in) then there is already a delivery date and outgoing route determined for that garment.'|| chr(10) ||'IF the last inscan date is more than X days  do normal processing'|| chr(10) ||'else'|| chr(10) ||'If the last inscan date is less than X days ago (X=value of new system setting) and X>0 '|| chr(10) ||'      if plannedoutdate is in the future '|| chr(10) ||'        then do not do any processing. '|| chr(10) ||'     else'|| chr(10) ||'        planned outdate in the past and X<>0 '|| chr(10) ||'        then do not create inscan, and do not increase washes, etc, only redetermine the planned out date/route ', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTLOGGETGARMENTDATA', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 ONLY Log Errors'|| chr(10) ||'1 Log each transaction, no details.   One row per transaction (per call)  '|| chr(10) ||'2 Log details.'|| chr(10) ||'Remind : to prevent large logs the setting 1 and 2 are only working 1 day (timestamp of this systemsetting)'|| chr(10) ||'the next day this setting is automatically set back to value 0.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTLOGSENDTRACKINFO', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 ONLY Log Errors'|| chr(10) ||'1 Log each transaction, no details.   One row per transaction (per call)  '|| chr(10) ||'2 Log details.'|| chr(10) ||'Remind : to prevent large logs the setting 1 and 2 are only working 1 day (timestamp of this systemsetting)'|| chr(10) ||'the next day this setting is automatically set back to value 0.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTROUTESTOP', 'A', 'C', 'A', 'N', 'N', null, null, 'A;D;Z;Y', 'Setting used for interface sortingsystem: sort on route stop:'|| chr(10) ||'A = Ascending'|| chr(10) ||'D = Descending'|| chr(10) ||'Y = Stopnr prefix are skipped in the sortstring. '|| chr(10) ||'Z = Customer and Stop prefix are skipped in the sortstring. '|| chr(10) ||'( Y only for residential )', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTSTOCKROOMDESTINATION', '0', 'S', '0', 'N', 'N', 0, 6, '', 'Defines the destination sort address to be used for items that have to be returned to stock. Although these items are already registered as returned to stock, they are considered as being in circulation so they can be handled via the sorting system because they need to be folded first via a folding machine bfore they will actually be put on stock physically. '|| chr(10) ||''|| chr(10) ||'Only relevant when procedure GerGarmentDataMetricon2 is used.', 'N');
execute CreateSystemSetting('Garment Recording', 'SORTSTRINGLENGTH', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Defines the length of the sortstring in the interface with sorting systems (GETGARMENTDATA procedure)'|| chr(10) ||'Value 1: Standard sortstring length of 60 characters'|| chr(10) ||'Value 2: Extended sortstring length of 80 characters. '|| chr(10) ||'Please be careful: discuss with your sorting system supplier before changing this setting.', 'N');
execute CreateSystemSetting('Garment Recording', 'TRACK_SER', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File directory for the ascii file TRACK.SER'|| chr(10) ||'For the export of the file TRACK.SER, which contains the scans', 'N');
execute CreateSystemSetting('Garment Recording', 'WORKORDERRESERVATION', '1', 'I', '1', 'N', 'N', 1, 4, '', '1 = Reservation should be done immediately'|| chr(10) ||'2 = Work order must be approved first before reservation (excluding replacement work orders)'|| chr(10) ||'3 = Manual selection between option 1 and 2'|| chr(10) ||'4 = Work order must be approved first before reservation (including replacement work orders)', 'N');
execute CreateSystemSetting('File Locations', 'ARCHIVEDIRMMMSTERILIZER', 'C:\ABSSOLUTE\IMP\ARCHIVE', 'S', 'C:\ABSSOLUTE\IMP\ARCHIVE', 'N', 'N', null, null, '', 'Archive directory for processed files coming from MMM sterilizers. ', 'N');
execute CreateSystemSetting('File Locations', 'ARCHIVEDIRUSEDORPACKS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Archive directory for used OR pack. Functionality implemented with module IMPORTUSEDORPACKS. ', 'N');
execute CreateSystemSetting('File Locations', 'COMMISSIONEXPORTDIR', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for extended commission calculation.', 'N');
execute CreateSystemSetting('File Locations', 'CSVEXPORTDIR', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module EXPORTOCSV. This is the directory where the CSV-file will be placed that is created when printing an invoice appendix of type "CSV File". Must be a valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'CUSTOMSFILEPATH', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'This setting holds the directory where the Customs CSV-file will be stored before sending it to the e-mail address which can be entered in the popup screen. Must be a valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'DATABASELOGDIR', 'C:\', 'S', 'C:\', 'N', 'N', 1, 60, '', 'Defines where the database should write log files. Used in'|| chr(10) ||'- conversion'|| chr(10) ||'- stored procedures for interface with sorting system.'|| chr(10) ||'Note: in Oracle parameter utl_file_dir should have * as value.', 'N');
execute CreateSystemSetting('File Locations', 'DELIVERYDOCEXPORTPATH', 'c:\abssolute\reportserver\pdfexport', 'S', '', 'N', 'N', null, null, '', 'Used to control where report PDF''s are put when automatically generated using the scheduled process - ProcessCreateDeliveryDocs.'|| chr(10) ||''|| chr(10) ||'Note this needs to be accessible by the report server', 'N');
execute CreateSystemSetting('File Locations', 'EDIFAKTDIRECTORY', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'The directory where the export file for EDIFAKT is created', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRAXAPTA', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for interface Axapta invoices', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRCLIEOP03', 'C:\ABSSOLUTE\EXPORT\CLIEOP03\', 'S', 'C:\ABSSOLUTE\EXPORT\CLIEOP03\', 'N', 'N', null, null, '', 'Only used for module CLIEOP03. This is the directory where the files for automatic collection must be placed. Must be a valid directory.', 'Y');
execute CreateSystemSetting('File Locations', 'EXPDIRCOBRA', 'C:\ABSSOLUTE\EXPORT\COBRA\', 'S', 'C:\ABSSOLUTE\EXPORT\COBRA\', 'N', 'N', null, null, '', 'Only used for module Export to Cobra. Directory on server where export file is created. Must be valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRDELNOTEINFO', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module EXPORTDELNOTEINFO. This is the directory where the CSV- files containing the delivery note data  should be put. Must be a valid directory accessible to the application.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRDELNOTEINFOGALAXIE', 'C:\ABSSOLUTE\EXP', 'S', 'C:\ABSSOLUTE\EXP', 'N', 'N', null, null, '', 'Export ROOT directory where the files with exported delivery note info for GALAXIE should be created. The file that will be picked up and processed by Galaxie will be created in a fixed SUB directory PO_DN_IN and a copy will be created in the SUB directory PO_DN_OUT.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the GALAXIE module is in the license', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIREDIINTERTRADE', 'EXPDIREDIINTERTRADE', 'S', 'EXPDIREDIINTERTRADE', 'N', 'N', null, null, '', 'This setting holds the main Oracle directory where the (outgoing) EDI export files created by the laundry will be put. Each message type (e.g. 855, 856, 810) will have its own sub folder within this main directory and for each message type a separate Oracle directory will have to be defined (e.g. EXPDIREDIINTERTRADE_855 etc.). The export will be started automatically from within a scheduled process. The data will be exported to a staging table first and it will be picked up by a separate scheduled process that actually creates the export file(s). '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module INTERTRADE is in the license', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIREDIPURCHASING', 'EDIPURCHASING_EXPORT', 'S', 'EDIPURCHASING_EXPORT', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the PO export files created for a supplier having option Send Order via EDI will be put. Each supplier will have its own subfolder. The export will be started from within the Purchase Order Status Control dialog when sending the PO to a supplier. The data will be exported to a staging table first and it will be picked up by a scheduled process that actually creates the export file(s). '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module EDIPURCHASING is in the license', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRETRA', 'C:\ABSSOLUTE\EXPORT\ETRA\', 'S', 'C:\ABSSOLUTE\EXPORT\ETRA\', 'N', 'N', null, null, '', 'Only used for module EXPORTINVOICESETRA. This is the directory where the files for exporting data to the ETRA Enterprise system must be placed. Must be a valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIREXACT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Directory for export Stock transactions to Exact.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIREXTINVOICE', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File location for export file printing invoices via external print company (Stralfors).', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRFIBUHTS', 'C:\ABSSOLUTE\EXPORT\HTS\', 'S', 'C:\ABSSOLUTE\EXPORT\HTS\', 'N', 'N', null, null, '', 'Only used for module HTSSTOCKTRANSACTIONS. This is the directory where the files for exporting data to the FIBU must be placed. Must be a valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRICBEXPORT', 'ICB\EXPORT', 'S', 'ICB\EXPORT', 'N', 'N', null, null, '', 'This setting holds the directory where the internal invoice export files will be put. The export will be started from within an external application, not from within the ABS client application. The data will be exported to a staging table first and it will be picked up by a separate process that actually creates the export file(s). '|| chr(10) ||'This setting is only relevant when module ICBINTERFACE is in the license', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRINDAUT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for Indaut interface.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRINVOICEBREAKDOWN', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module INVOICEBREAKDOWN. This is the server directory where the CSV- file containing the invoice breakdown data  should be put. Must be a valid directory accessible to the database server.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRITELLA', 'C:\ABSSOLUTE\EXPORT\ITELLA\', 'S', 'C:\ABSSOLUTE\EXPORT\ITELLA\', 'N', 'N', null, null, '', 'Only used for module EXPORTINVOICESITELLA. This is the directory where the files for exporting invoices to the Itella Printing Company must be placed. Must be a valid directory.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRLCTSORT', 'C:\ABSSOLUTE\EXPORT\LCT\', 'S', 'C:\ABSSOLUTE\EXPORT\LCT\', 'Y', 'N', null, null, '', 'Only used for module INTERFACELCTSORT. This is the (server) directory where the ASCII-file(s) for exporting data to the LCT Sorting system must be placed. Must be a valid directory. ', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRLEANLIFT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Path to put file for export Leanlift (only applicable for module LEANLIFT)', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRMATSORT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for module MATSORTINTERFACE.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRPDA', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for PDA interface with 3rd party PDA software. Not used with ABS PDA software.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRPURCHASEORDER', 'C:\ABSSOLUTE\EXP\PURCHASEORDERS', 'S', 'C:\ABSSOLUTE\EXP\PURCHASEORDERS', 'N', 'N', null, null, '', 'Directory for export purchase orders.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRROUTEPLANNER', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'This is the directory where the export file to Route Planner Software will be created. ', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRSALESFORCE', 'C:\', 'S', 'C:\', 'N', 'N', 1, 60, '', 'Defines where the SalesForce export procedures will export the output files.'|| chr(10) ||''|| chr(10) ||'Note: in Oracle parameter utl_file_dir should have * as value. Oracle must be able to write in the selected directory.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRSOILTICKET', 'C:\ABSSOLUTE\EXP', 'S', 'C:\ABSSOLUTE\EXP', 'N', 'N', null, null, '', 'Export directory for Soil Ticket info to external soil count systems (i.e. VAC systems)', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRSOILWEIGHINGS', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'This system setting is used only when the module SOILWEIGHTEXPORT is in the license of the plant. '|| chr(10) ||'The file path of the file where the soil weighing ticket lines are exported is configured via this system setting. Mind that the file name should not be entered here.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRSTOCKCOUNT', 'C:\ABSSOLUTE\EXP', 'S', 'C:\ABSSOLUTE\EXP', 'N', 'N', null, null, '', 'Directory where export stock count for Easy and MobiDik will put the created files.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRSTOCKHANDLING', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for stockroom orders', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRTVN', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'location to export delivery notes', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRVL', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module VLInterface. This is the server/client directory where the CSV-files for exporting data to Virtual Laundry must be placed. Must be a valid directory. ', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRWEBSALES', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'File location for exports for module WMUWEBSALES.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRWIPERSTICKER', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for Wiper stickers', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRWOAXAPTA', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Axapta interface: valid path where Abssolute puts the XML files for Axapta.', 'N');
execute CreateSystemSetting('File Locations', 'EXPDIRXMLORDERFORM', '-', 'S', '-', 'Y', 'N', null, null, '', 'Location where the XML data will be exported to. This data is exported from within the Route Status Control dialog when the Route List is printed, or from within the Stops sub-dialog. This is triggered in the same way as normally the Order Form report is printed.'|| chr(10) ||''|| chr(10) ||'Only of any importance in case XML Orderform is developped for you as custom made solution', 'N');
execute CreateSystemSetting('File Locations', 'EXPORTDIRCNTUSAGERPT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module KNT. This is the directory where the PDF-files containing the container info per stop will be exported by process Send Container Usage Report by E-mail. Must be a valid directory accessible to the application.', 'N');
execute CreateSystemSetting('File Locations', 'EXPORTDIRLCTTRANS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Export directory for LCT transactions file. Generated when the delivery notes is finalized (printed) This is the  ''TRANSSN<note-nr>.ASC'' file, that is renamed to TRANSSC.ASC and placed on an FTP server.'|| chr(10) ||'Only applicable with module LCTTRANSACTIONS', 'N');
execute CreateSystemSetting('File Locations', 'EXPORTDIRPROTEUS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Directory for creating export file Interface Proteus', 'N');
execute CreateSystemSetting('File Locations', 'EXPORTPLANNERFILENAME', 'Ext-ACCESS-Auftrag.csv', 'S', 'Ext-ACCESS-Auftrag.csv', 'Y', 'N', null, null, '', 'This is the file where the export file to Route Planner Software will be created. ', 'N');
execute CreateSystemSetting('File Locations', 'EXPWEEKLYVARIATIONS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File location (path) for export file for weekly variations (only applicable for this module).', 'N');
execute CreateSystemSetting('File Locations', 'EXTERNALPRICEUPDATEPATH', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module EXTERNALPRICEUPDATE. This setting holds the directory where the prices CSV file will be exported as well as the directory to be used during import.', 'N');
execute CreateSystemSetting('File Locations', 'FINEXPDIRDAILYSYSTEM', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Directory for export invoices to daily system (only applicable for module)', 'N');
execute CreateSystemSetting('File Locations', 'FINEXPORTDIRECTORY', 'FINEXPORTDIR', 'S', 'C:\', 'N', 'N', null, null, '', 'Bookkeeping system export file location at the application server machine. '|| chr(10) ||''|| chr(10) ||'When system setting BOOKKEEPINGSYTEM is set to 11 (Export via custom stored procedure) then this setting specifies the Oracle Directory name. Ask ABS to create/configure this Oracle Directory.', 'N');
execute CreateSystemSetting('File Locations', 'FINIMPORTDIRECTORY', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'Bookkeeping system import file location at the application server machine. '|| chr(10) ||''|| chr(10) ||'When system setting BOOKKEEPINGSYTEM is set to 11 (Export via custom stored procedure) then this setting specifies the Oracle Directory name. Ask ABS to create/configure this Oracle Directory.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRAXAPTA', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for Axapta interface invoices', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRBUNDLEIMPORT', 'C:\BUNDLEIMPORT', 'S', 'C:\BUNDLEIMPORT', 'N', 'N', null, null, '', 'The directory where the bundle system will put it''s export files.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRDELIVERYNOTES', 'C:\', 'S', 'C:\', 'N', 'Y', null, null, '', 'Import directory for delivery notes.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIREDIINTERTRADE', 'IMPDIREDIINTERTRADE', 'S', 'IMPDIREDIINTERTRADE', 'N', 'N', null, null, '', 'This setting holds the main Oracle directory where the EDI purchase order import files created by a laundry customer will be put. Each message type (e.g. 850) will have its own sub folder within this main directory and for each message type a separate Oracle directory is expected (e.g. IMPDIREDIINTERTRADE_850). The import files will be picked up by a scheduled process that actually processes the purchase order data to a staging table first and it will be picked up by a separate scheduled process that actually creates customer orders in ABS. . '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module INTERTRADE is in the license', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIREDIINTERTRADE_ARCH', 'IMPDIREDIINTERTRADE_ARCH', 'S', 'IMPDIREDIINTERTRADE_ARCH', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the EDI purchase order (850) import files that were imported successfully will be put, to avoid that they will be processed more than once. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module INTERTRADE is in the license', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIREDIINTERTRADE_FAIL', 'IMPDIREDIINTERTRADE_FAIL', 'S', 'IMPDIREDIINTERTRADE_FAIL', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the EDI purchase order (850) import files that could not be imported will be moved to,  to avoid that they will be processed more than once. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module INTERTRADE is in the license', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIREDIPURCHASING', 'EDIPURCHASING_IMPORT', 'S', 'EDIPURCHASING_IMPORT', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the PO confirmation files created by a supplier having option Send Order via EDI will be put. Each supplier will have its own subfolder. The import files will be picked up by a scheduled process that actually processes the confirmation data back into ABS. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module EDIPURCHASING is in the license', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIREDIPURCHASING_ARCH', 'EDIPURCHASING_IMPORT_ARCH', 'S', 'EDIPURCHASING_IMPORT_ARCH', 'N', 'N', null, null, '', 'This setting holds the Oracle directory where the imported PO confirmation files, created by a supplier having option Send Order via EDI, will be moved to after being imported. Each supplier will have its own subfolder. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module EDIPURCHASING is in the license', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRHL7', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'Directory where the file to be imported for HL7 connection are found by ABSSolute. ', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRINDAUT', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for INDAUT interface', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRINTERNETDELNOTES', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Full path where the import file can be found for importing delivery notes created via a web application. Only appliable for module INTERNETDELNOTES.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRORDERS', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'File location for imports from web ordering module into ABSSolute.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRPDS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for PDS.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRPWBASSIGN', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for product assign info file.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRSOILCOUNT', 'C:\ABSSOLUTE\IMP', 'S', 'C:\ABSSOLUTE\IMP', 'N', 'N', null, null, '', 'Import directory for Soil Ticket info from external soil count systems (i.e. VAC systems)', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRSOILSCAN', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory from soil scan interface. The import file will be taken from this directory. The directory is a server directory.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRSOILSCANORACLE', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Path from import directory for soilscan files as local path on the Oracle server.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRSTOCKCOUNT', 'C:\ABSSOLUTE\IMP', 'S', 'C:\ABSSOLUTE\IMP', 'N', 'N', null, null, '', 'Directory where is located file for import stock count from Easy and MobiDik.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRSTOCKHANDLING', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for stock transactions, stock handling interface.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRWEBSALES', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'File location for imports for module WMUWEBSALES.', 'N');
execute CreateSystemSetting('File Locations', 'IMPDIRWOAXAPTA', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Valid path to directory where Axapta puts the XML files for Abssolute (for Axapta interface).', 'N');
execute CreateSystemSetting('File Locations', 'IMPORTDIRLCTTRANS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory from where TRANSVL.ASC file is located on server.'|| chr(10) ||'This is typically /GDTransactions/ImpExp/600010/upload'|| chr(10) ||'Used by the Import LCT Transactions scheduled process.'|| chr(10) ||'Only applicable with License module LCTTRANSACTIONS', 'N');
execute CreateSystemSetting('File Locations', 'IMPORTDIRMMMSTERILIZER', 'C:\ABSSOLUTE\IMP', 'S', 'C:\ABSSOLUTE\IMP', 'N', 'N', null, null, '', 'Import directory for sterilization information coming from MMM sterilizers. ', 'N');
execute CreateSystemSetting('File Locations', 'IMPORTDIRUSEDORPACKS', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Import directory for used OR pack. Functionality implemented with module IMPORTUSEDORPACKS. ', 'N');
execute CreateSystemSetting('File Locations', 'IMPTREATMENTRESULT', 'C:\', 'S', 'C:\', 'Y', 'N', 3, 40, '', 'The system setting defines  where 3rd party application will save Treatment resultfiles.', 'N');
execute CreateSystemSetting('File Locations', 'INVOICEJOBLOGDIR', 'c:\', 'S', 'c:\', 'N', 'N', null, null, '', 'Directory name (full path name) for log files from invoice job generation. Only applicable for the module invoicejobs.', 'N');
execute CreateSystemSetting('File Locations', 'PATHFORTRANSFERGDINFO', 'C:\ABSSOLUTE\SERVER\EXPORTGD\', 'S', 'C:\ABSSOLUTE\SERVER\EXPORTGD\', 'N', 'N', null, null, '', 'The system setting PATHFORTRANSFERGDINFO will contain the path on the server where export and import ASCII file will be stored for interfacing with Garment Dispenser.', 'N');
execute CreateSystemSetting('File Locations', 'PDFEXPORTPATH', 'c:\abssolute\reportserver\pdfexport', 'S', 'c:\abssolute\reportserver\pdfexport', 'N', 'N', null, null, '', 'File system folder location for storing PDF documents of any documenttype – to be sent as an attachment by the Abssolute Email processes.'|| chr(10) ||'This folder must be accessible by the report server process and the application server process'|| chr(10) ||'When multiple reportservers/applicationservers are used, it is recommended to use a shared folder.'|| chr(10) ||'Under this folder, the system will create a subfolder for every customer.', 'N');
execute CreateSystemSetting('File Locations', 'PRINTBATCHPATH', 'C:\ABSSOLUTE\SERVER\BIN\', 'S', 'C:\ABSSOLUTE\SERVER\BIN\', 'N', 'Y', null, null, '', 'The system setting PRINTBATCHPATH will contain the path on the server where *.BAT files, used to print ASCII reports, are located.', 'N');
execute CreateSystemSetting('File Locations', 'PUTUPDOCEXPORTPATH', 'c:\abssolute\reportserver\pdfexport', 'S', '', 'N', 'N', null, null, '', 'Used to control where report PDF''s are put when automatically generated using the scheduled process - ProcessCreatePutUpDocs.'|| chr(10) ||''|| chr(10) ||'Note this needs to be accessible by the report server', 'N');
execute CreateSystemSetting('File Locations', 'REPORT_PATH', 'C:\ABSSOLUTE\REPORTS\', 'S', 'C:\ABSSOLUTE\REPORTS\', 'N', 'N', null, null, '', 'Directory where the Crystal reports (.RPT files) are located.'|| chr(10) ||'Not used for I-Net.', 'Y');
execute CreateSystemSetting('File Locations', 'ROUTECHANGESIMPFILENAME', 'C:\NEWROUTE.TXT', 'S', 'C:\NEWROUTE.TXT', 'N', 'N', null, null, '', 'Filename (including path) for the import of route info from the route optimizing interface.', 'N');
execute CreateSystemSetting('File Locations', 'ROUTEOPTIMIZINGEXPFILENM', 'C:\ABSCRMSD.RPS', 'S', 'C:\ABSCRMSD.RPS', 'N', 'N', null, null, '', 'Filename (including path) for the export of route info for the external route optimizing interface.', 'N');
execute CreateSystemSetting('File Locations', 'SERVERTEMPFOLDER', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'This setting refers to a temp folder on the Abssolute server. This folder can be used to write temporary files by processes that run on the server. The server must have read/write access to this folder. The folder must be an existing foldername.', 'N');
execute CreateSystemSetting('File Locations', 'SOILREASDOCEXPORTPATH', 'c:\abssolute\reportserver\pdfexport', 'S', '', 'N', 'N', null, null, '', 'Used to control where report PDF''s are put when automatically generated using the scheduled process - ProcessCreateSoilReasonability.'|| chr(10) ||''|| chr(10) ||'Note this needs to be accessible by the report server', 'N');
execute CreateSystemSetting('File Locations', 'SORTBATCHEXPORTDIR', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'File path where the export of the sort batch is put. This is a directory on the local client, not on the server.  Only applicabble if module Sortingsystem is available and Sortingsysteminterface 1 (via ASCII file) is used.', 'N');
execute CreateSystemSetting('File Locations', 'WEBCSVEXPORTDIR', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'This is the directory where the XLS and CSV-files will be placed when web layouts are exported in xls or csv format .Must be a valid directory.', 'N');
execute CreateSystemSetting('E-Mail settings', 'EDITABLEEMAILSTATUSINV', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, the email status is editable in maintain invoices allowing to resend or prevent the invoice to be emailed. It is only allowed to be changed when the customer is set to be send by email.', 'N');
execute CreateSystemSetting('E-Mail settings', 'EMAILCOMBINEPERIODINVOICE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether individual periodical invoices that have a split-up code (even when belonging to different customers and/or cost centers) that are supposed to be sent to the same email address, should be sent as multiple emails or if they should be combined into 1 single email.'|| chr(10) ||'0 = The invoices will be sent one by one'|| chr(10) ||'1 = The invoices will be combined into 1 single email'|| chr(10) ||''|| chr(10) ||'This setting is only considered as of release 9.08.01', 'N');
execute CreateSystemSetting('E-Mail settings', 'EMAILMERGEPDF', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = PDF documents are attached as presented.'|| chr(10) ||'1 = Invoice mail merge invoice with appendices into 1 single PDF document'|| chr(10) ||'2 = Same as 1, but child invoices are not merged for consolidated invoices'|| chr(10) ||''|| chr(10) ||'Option 2 is only available as of release 9.03.00', 'N');
execute CreateSystemSetting('E-Mail settings', 'EMAILPDFMAXIMUMSIZE', '25', 'I', '25', 'N', 'N', 0, 9999, '', 'The maximum size (in MB) of pdf that can be automatically sent as an email attachment.'|| chr(10) ||'If the generated pdf is over this size, we will not attempt to send it.'|| chr(10) ||''|| chr(10) ||'Currently only implemented for statements.', 'N');
execute CreateSystemSetting('E-Mail settings', 'EMAILPDFPREFIX', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No variable prefix (also remove the underscore separator).'|| chr(10) ||'1 = Variable prefix is filled with the DelToCustomerNumber of the invoice. The email receiver can use this number to sort the invoices on their local environment. The DelToCustomerNumber is not added to a consolidated invoice.'|| chr(10) ||'Note: the variable prefix is not (yet) implemented for direct (US) invoicing and for client invoices. The prefix is also not added for user defined export (CSV) files. ', 'N');
execute CreateSystemSetting('E-Mail settings', 'EMAILVIASECURESMTPS', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Communication for sending e-mail via secured smtps or not secured smtp.'|| chr(10) ||'For mail relay, or outdated SMTP communication the setting should be N.', 'N');
execute CreateSystemSetting('E-Mail settings', 'INVOICEPDFCREATIONQTY', '1', 'I', '1', 'N', 'N', 1, 9999, '4', 'When creating a statement with merged invoice pdf''s we can create the pdfs to merge per invoice (so create one pdf per invoice and then merge them all - this setting on 1) or create multiple invoices as separate pdfs (this setting more than 1) and then merge them.  '|| chr(10) ||''|| chr(10) ||'This is done for performance reasons and is a balance between creating many smaller pdfs to merge and less but larger pdf''s to merge.'|| chr(10) ||''|| chr(10) ||'When the report server is creating a large pdf (many invoices), its 100% utilised for that task so may cause performance issues for other processes trying to generate reports if this value is too large.', 'N');
execute CreateSystemSetting('E-Mail settings', 'MAILPORT', '25', 'I', '587', 'N', 'Y', 1, 65535, '', 'Defines the MAILPORT of the SMTP server configured for sending emails from ABSSolute. '|| chr(10) ||'Use port 587 for a secure channel. '|| chr(10) ||'Use port 25 for unencrypted mailtraffic.', 'N');
execute CreateSystemSetting('E-Mail settings', 'MAILUSERNAME', 'username@domain.com', 'S', 'username@domain.com', 'N', 'N', null, null, '', 'Username to authenticate at the SMTP server used to send emails from Abssolute.'|| chr(10) ||'The FROM: address is specified in the E-mail Settings dialog per document type.'|| chr(10) ||'Note: If this is setting is changed and BI email agents are in use via the same email address, do not forget to ask ABS to make this change in the BI server configuration as well.', 'N');
execute CreateSystemSetting('E-Mail settings', 'MAILUSERPASSWORD', 'xxxxxxxx', 'S', 'xxxxxxxx', 'N', 'N', null, null, '', 'Password of the useraccount to authenticate at the SMTP server. '|| chr(10) ||'Useraccount name is defined in setting MAILUSERNAME'|| chr(10) ||'Note: If this is setting is changed and BI email agents are in use via the same email address, do not forget to ask ABS to make this change in the BI server configuration as well.', 'N');
execute CreateSystemSetting('E-Mail settings', 'MAXSTATEMENTSIZEFOREMAIL', '60000', 'I', '60000', 'N', 'N', 0, 999999, '', 'This setting can be used to stop invoice pdf''s being created and merged for a statement if the number of invoice pdfs is too many as this may cause the pdf merge process to fail, crashing the whole statement email process.'|| chr(10) ||''|| chr(10) ||'This is a problem for bill to customers with many del to customers with debts (open ARTransaction)'|| chr(10) ||''|| chr(10) ||'So if the customer is set to send statements by email with attached invoice copies and merge to pdf and there are more than this settings number of invoices lines on these invoices on the statement then the generate and merge process will be skipped and no invoices will be attached to the statement.'|| chr(10) ||''|| chr(10) ||'The value of 60,000 has been determined in one particular environment but this may need to be adjusted depending on the customers system resources.', 'N');
execute CreateSystemSetting('E-Mail settings', 'MICROSOFTCLIENTID', '-', 'S', '', 'N', 'N', null, null, '', 'Microsoft Entra ClientID. Works only if MICROSOFTGRAPH set on Y', 'N');
execute CreateSystemSetting('E-Mail settings', 'MICROSOFTCLIENTSECRET', '-', 'S', '', 'N', 'N', null, null, '', 'Microsoft Entra Client Secret. Works only if MICROSOFTGRAPH set on Y', 'N');
execute CreateSystemSetting('E-Mail settings', 'MICROSOFTGRAPH', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set on YES, ABSSOLUTE will use Microsoft Graph instead of SMTP when sending E-mails', 'N');
execute CreateSystemSetting('E-Mail settings', 'MICROSOFTTENANTID', '-', 'S', '', 'N', 'N', null, null, '', 'Microsoft Entra TenantID. Works only if MICROSOFTGRAPH set on Y', 'N');
execute CreateSystemSetting('E-Mail settings', 'SENDEMAILCONSIGNMENTNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = All consignment notes for which the customer is set to send by email and which have not yet been send are send.'|| chr(10) ||'1 = Only consigment notes for which the customer is set to send by email and which have not yet been send up until the current date are send. So the consignment note is send on the delivery date.', 'N');
execute CreateSystemSetting('E-Mail settings', 'SMTPSERVERNAME', 'mail.com', 'S', 'mail.com', 'N', 'N', null, null, '', 'Defines the SMTP server name in use to send emails from ABSSolute. '|| chr(10) ||'This server must be reachable from the ABSSolute application server(s) using the ports configured with setting MAILPORT.'|| chr(10) ||'Note: If this is setting is changed, and BI email agents are in use, do not forget to ask ABS make this change in the BI server configuration as well.', 'N');
execute CreateSystemSetting('WebApplication', 'ABSWEBPORTALURL', 'http://mylaundry.com', 'S', '-', 'Y', 'N', null, null, '', 'This system setting contains the value of the URL for the web portal application powered by ABS.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWCHANGEQTYDEFAULTINV', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'The inventory for a wearer employment is copied from the default inventory (from function). This setting specifies whether the user is allowed to change this default quantity.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWCREATEBUDGADJSTMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it must be possible to create Budget Transactions via the web portal or not.  This will be granted only for web user that have been setup accordingly. Possible values:'|| chr(10) ||'0 = Do not allow to create budget adjustments via the web portal (default)'|| chr(10) ||'1 = Do allow to create budget adjustments via the web portal'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the BKLINTERNET and WEARERGARMENTSBUDGET modules are both in the license.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWEMPTYSTOCKCOUNTORDER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be obligated to enter at least one quantity for the products to be ordered/counted from within the Stock Count / Order form in the web portal for a given count day for a consumption point, otherwise it will not be possible to save/confirm any counts or ordered quantities.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Confirm/save is always enabled, even when no quantities have been entered (standard behaviour)'|| chr(10) ||'1 = Confirm/save is only enabled when at least one quantity has been entered', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWLATEWEBORDERS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is used to control whether it is allowed to create new WEB ORDERS via the ORDER ENTRY form for a certain delivery date when there already exist any packing notes for that particular delivery date.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = No  '|| chr(10) ||'1 = Yes'|| chr(10) ||'2 = Yes with warning. '|| chr(10) ||''|| chr(10) ||'When set to 1, then a new web order can be created without any restriction regarding the existence of any packing notes for the delivery date.'|| chr(10) ||'When set to 0, then no new web order can be be created and an error-message will be displayed, containing the text that is stored in system setting LATEWEBORDERERROR.'|| chr(10) ||'When set to 2, then a warning is displayed, containing the text as stored in system setting LATEWEBORDERWARNING. However, it is still possible to create a new web order.'|| chr(10) ||''|| chr(10) ||'This setting is NOT considered when creating INTERNET ORDERS via the STOCK COUNT / ORDERING form.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWMOVECLIENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This settings is only used in the residential web portal (new web application). When set to 1, in the web user is added a checkbox to allow to move a client to another customer. A client can only be moved to a customer to which the web user has access.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWMOVEWEARER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the functionality should be enabled that allows an authorized web user to move a wearer from one customer to another customer. At web user level one can define if a particular web user should have the possibility to use this functionality or not.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 = Not allowed.'|| chr(10) ||'1 = Allowed.', 'N');
execute CreateSystemSetting('WebApplication', 'ALLOWWEBORDERPASTDEADLINE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if a web order can still be created and approved although the dead line has passed.  It is either not allowed, allowed without asking for confirmation, or allowed when the timeframe was extended by the laundry. Possible values:'|| chr(10) ||'0 = Do not allow to order past deadline'|| chr(10) ||'1 = Allow to order past deadline'|| chr(10) ||'2 = Allow to order past deadline within graceperiod'|| chr(10) ||''|| chr(10) ||'Only relevant when system setting SHOWCOUNTDEADLINESTOCUST = Y', 'N');
execute CreateSystemSetting('WebApplication', 'BIANALYSISLANDINGPAGE', '-', 'S', '-', 'N', 'N', null, null, '', 'Defines the name of the BI analysis that is shown below the welcome message at the landing page after login (or after choosing the customer) at the customer web portal.'|| chr(10) ||'Value - means no BI analysis will be shown at the landing page.'|| chr(10) ||'The folder location of the BI analysis has to be the one defined by the system setting BIROOTPATH, just like other BI content in the customer web portal.'|| chr(10) ||'Note: this requires module Web Portal Business Intelligence', 'N');
execute CreateSystemSetting('WebApplication', 'BIPASSWORD', 'PASSWORD', 'S', 'PASSWORD', 'N', 'N', null, null, '', 'Password which the web portal uses to log on to the BI system'|| chr(10) ||'Only relevant when module Web Portal Business Intelligence is licensed.'|| chr(10) ||'Do not use ampersand sign in password.', 'N');
execute CreateSystemSetting('WebApplication', 'BIROOTPATH', '/shared/Custom Answers/Web Portal/', 'S', '/shared/Custom Answers/Web Portal/', 'N', 'N', null, null, '', 'Root path for the BI analysis.'|| chr(10) ||'Only relevant when module Web Portal Business Intelligence is licensed.', 'N');
execute CreateSystemSetting('WebApplication', 'BISERVERNAME', 'biservername', 'S', 'biservername', 'N', 'N', null, null, '', 'Name or IP# of BI server.'|| chr(10) ||'Only relevant when module Web Portal Business Intelligence is licensed.'|| chr(10) ||'(do not include http or https in name)'|| chr(10) ||'Note: for this to work the BI server must be accessible from outside.', 'N');
execute CreateSystemSetting('WebApplication', 'BISERVERPORT', '443', 'I', '443', 'N', 'N', 0, 99999, '', 'TCP/IP Port number at which the BI server can be accessed.'|| chr(10) ||'Only relevant when module Web Portal Business Intelligence is licensed.'|| chr(10) ||'Note: for this to work the BI server must be accessible from outside.', 'N');
execute CreateSystemSetting('WebApplication', 'BITOOL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines which BI tool content can be embedded in the customer webportal'|| chr(10) ||'0 = Oracle BI classic analysis only - default'|| chr(10) ||'1 = Oracle BI classic analysis and Oracle analytics workbooks'|| chr(10) ||''|| chr(10) ||'Note: only put on 1 when Oracle Analytic Service (OAS) is installed AND useOAS setting in web.xml configuration is set to Y.', 'N');
execute CreateSystemSetting('WebApplication', 'BIUHFMONITORDASHBOARDPATH', 'shared/Custom Dashboards/_Portal/UHFMon', 'S', 'shared/Custom Dashboards/_Portal/UHFMon', 'N', 'N', null, null, '', 'Path for the UHF Monitor dashboard in BI'|| chr(10) ||'Only relevant when module UHFBUFFER and module BUSINESSINTELLIGENCE are both licensed.', 'N');
execute CreateSystemSetting('WebApplication', 'BIUSERNAME', 'WEBPORTAL', 'S', 'WEBPORTAL', 'N', 'N', null, null, '', 'User name which the web portal uses to log on to the BI system'|| chr(10) ||'Only relevant when module Web Portal Business Intelligence is licensed.', 'N');
execute CreateSystemSetting('WebApplication', 'BIUSEWEBUSERLANGUAGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if the language of the webuser should be used when showing embedded BI content.'|| chr(10) ||'0 = No'|| chr(10) ||'1 = Yes'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module BI Web portal integration is in use and multi-lingual BI is enabled.'|| chr(10) ||''|| chr(10) ||'After changing this setting the web server needs to be restarted.'|| chr(10) ||'After changing this setting from 1 to 0 local browser cache needs to be cleared in order to show BI content in browser language.', 'N');
execute CreateSystemSetting('WebApplication', 'BIVIASECUREHTTP', 'Y', 'B', 'Y', 'N', 'N', null, null, 'YN', 'This setting controls whether HTTPS will be used to construct the URL for accessing the BI server. Possible values:'|| chr(10) ||'N = call server using http:// :port#          '|| chr(10) ||'Y = call server using https:// :port#'|| chr(10) ||''|| chr(10) ||'Related to settings BISERVERNAME en BISERVERPORT. Only relevant when module Web Portal Business Intelligence is licensed.', 'N');
execute CreateSystemSetting('WebApplication', 'CHGMAXEDITABLEONWEB', '0', 'I', '0', 'N', 'Y', 0, 3, '', 'Defines whether the fields "Max Inventory" and "Changes Per Week" are editable in the Garment Web Application when adding or modifying a wearer inventory line. '|| chr(10) ||'0 = Both fields are editable'|| chr(10) ||'1 = Only "Changes Per Week" is editable'|| chr(10) ||'2 = Only "Max Inventory" is editable'|| chr(10) ||'3 = Either one of the two fields is editable, depending on the selected billing method.'|| chr(10) ||'      "Changes Per Week" is editable in case of billing method 1'|| chr(10) ||'      "Max Inventory" is editable when billing method <> 1 '|| chr(10) ||''|| chr(10) ||'The value of this setting will be used in combination with the setting CHANGESWEEKRELATEDTOMAX', 'N');
execute CreateSystemSetting('WebApplication', 'CLIENTDELNOTEHISTORY', '13', 'I', '13', 'N', 'N', 0, 999, '', 'Maximum number of weeks for client delivery notes to be shown in the past in the web application.'|| chr(10) ||'0 = Current week only'|| chr(10) ||'1 = Current week + 1 week in the past.'|| chr(10) ||'Etc.', 'N');
execute CreateSystemSetting('WebApplication', 'CLIENTINVOICESHISTORY', '13', 'I', '13', 'Y', 'Y', 0, 53, '', 'This setting controls the number of weeks in the past for which any client invoices should be displayed on the Invoices tab of the "Client" form in the ABS Web Application. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Current week'|| chr(10) ||'1 = Current week + previous week'|| chr(10) ||'2 = Current week + last 2 weeks'|| chr(10) ||'Etc.'|| chr(10) ||'Default is 13 (so current week + 13 weeks in the past).', 'N');
execute CreateSystemSetting('WebApplication', 'CLIENTSCANHISTORY', '13', 'I', '13', 'N', 'N', 0, 99, '', 'Number of weeks shown in the scan history in the web application for residential services.'|| chr(10) ||'0 = Curent week only'|| chr(10) ||'1 = current week + 1 week in the past'|| chr(10) ||'etc.', 'N');
execute CreateSystemSetting('WebApplication', 'CONTACTCATFORLOSSANDFOUND', '-', 'S', '-', 'N', 'N', null, null, '', 'this defines the contact category used for creating loss and found contact messages from My Uniform Assistant', 'N');
execute CreateSystemSetting('WebApplication', 'CONTACTUPDATEDURINGRCI', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This defines what controls are in place for the WebX Route check in contacts tab '|| chr(10) ||'0 = no controls'|| chr(10) ||'1 = status are changed when follow up notes are added and all contacts must be updated before settlement can be run.  See X-RouteCheckInDlg for details of constraints', 'N');
execute CreateSystemSetting('WebApplication', 'DEFAULTPASSWEXPIRATION', '30', 'I', '30', 'Y', 'N', 1, 999, '', 'Default number of days the password is valid. After the password is expired, the web user must change first the password at the next login.', 'N');
execute CreateSystemSetting('WebApplication', 'DELIVERYPOLICY', '-', 'S', '-', 'N', 'N', 1, 40, '', 'This is the path and filename (including extension) to a pdf file containing the delivery conditions. If defined, on the screen appears the text "Click here to view our delivery conditions.". The word here is underlined and a hyperlink. When clicked, the pdf document is shown.'|| chr(10) ||''|| chr(10) ||'Dropped, file will be placed on fixed location, and multilingual', 'Y');
execute CreateSystemSetting('WebApplication', 'DELOBSOLETEINTERNETORDERS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether any existing internet orders that are no longer considered relevant may be deleted when entering new orders for a count day. An internet order is considered irrelevant when it has not been counted yet, or when it has been counted but not been confirmed when trying to create a new order for this consumption point. When it concerns an order that has been counted but not been confirmed, then a web user may be asked for confirmation if they may be deleted or not.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do delete existing orders that have not been counted yet and ask for confirmation when they have already been counted'|| chr(10) ||'1 - Do not delete any existing orders, regardless of the fact whether they have been counted or not and do not ask the user for confirmation'|| chr(10) ||''|| chr(10) ||'This setting only applies to LVMINTERNET', 'N');
execute CreateSystemSetting('WebApplication', 'EMBLEMTEMPLATEACCESS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Define if the web user could chnage the emblem template on wearer level in new web application.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Modifiable (default)'|| chr(10) ||'1 = Not modifiable', 'N');
execute CreateSystemSetting('WebApplication', 'EXTENDEDWEARERSEARCH', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Define if the web user could search for wearers only for current customer or for all customers linked to the web user.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = standard wearer search (default value)'|| chr(10) ||'1 = extended wearer search', 'N');
execute CreateSystemSetting('WebApplication', 'HIDESAVEANDNEXTBUTTON', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to directly jump to the next consumption point to be counted for the current count schedule from within the Stock Count / Order form in the web portal. If it is intended to be possible, then a Save/Confirm & Next will be shown besides the Save/Confirm & Close button, otherwise it will only show a Save/Confirm & Close button. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Save & Next is always shown when there is a next consumption point to be counted (standard behaviour)'|| chr(10) ||'1 = Save & Next is never shown, regardless of the fact if there is a next consumption point to be counted or not', 'N');
execute CreateSystemSetting('WebApplication', 'LATEWEBORDERERRORMSG', 'It is not allowed to create new orders.', 'S', 'It is not allowed to create new orders.', 'N', 'N', 1, 100, '', 'Only applicable when the module LVMINTERNET is active. Used in combination with the system settings ALLOWLATEWEBORDERS and LATEWEBORDERWARNING.'|| chr(10) ||''|| chr(10) ||'This setting holds the error message that will be displayed when a web user tries to create a new web order for a customer department on a delivery date for which there already exists any packing notes. This error message will be displayed when the system setting ALLOWLATEWEBORDERS is set to 0 ( = No).', 'N');
execute CreateSystemSetting('WebApplication', 'LATEWEBORDERWARNING', 'It is not recommended to create orders.', 'S', 'It is not recommended to create orders.', 'Y', 'N', 1, 100, '', 'Only applicable when the module LVMINTERNET is active. Used in combination with the system settings ALLOWLATEWEBORDERS and LATEWEBORDERERRORMSG.'|| chr(10) ||''|| chr(10) ||'This setting holds the warning that will be displayed when a web user tries to create a new web order for a customer department on a delivery date for which there already exists any packing notes. This warning will be displayed when the system setting ALLOWLATEWEBORDERS is set to 2 ( = Yes with warning).', 'N');
execute CreateSystemSetting('WebApplication', 'LIMITEDSIZESELECTION', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether a web user may select all sizes when adding a new wearer inventory, or only  may select sizes that are marked as standard length within the size group defined on product-size level.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 = Full access. Checkbox Limited size selection on webuser level is not checked for a new web user'|| chr(10) ||'1 = Limited access. Checkbox Limited size selection is automatically set to checked for a new web user.'|| chr(10) ||''|| chr(10) ||'Depending of the value FIXED or DEFAULT the user is allowed to change the attribute for a web user.', 'N');
execute CreateSystemSetting('WebApplication', 'MINPASSWLENGTH', '8', 'I', '8', 'Y', 'N', 4, 20, '', 'Minimum length of password. Only used in combination with passwordcomplexity = 1', 'N');
execute CreateSystemSetting('WebApplication', 'MSG_INTERNET_LOGIN', 'Welcome', 'S', 'Welcome', 'N', 'N', null, null, '', 'This message appears on the screen when a web user logs in to internet application.', 'N');
execute CreateSystemSetting('WebApplication', 'MYUNIFORMASSISTANTURL', 'http://mylaundry.com', 'S', '', 'Y', 'N', null, null, '', 'This system setting contains the value of the URL for My Uniform Assistant Web Application.', 'N');
execute CreateSystemSetting('WebApplication', 'NEWWEBAPPLICATION', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Must be set to yes if  redesigned web application is used.', 'N');
execute CreateSystemSetting('WebApplication', 'ORDERDEADLINECALCULATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the order deadline in the web portal will be shown (and stored) using the timezone of the customer, or using the timezone of the plant of the web user. Possible values:'|| chr(10) ||'0 - Use the time zone of the plant of the web user (default).'|| chr(10) ||'1 - Use the time zone of the customer.'|| chr(10) ||''|| chr(10) ||'This setting is in fact only relevant when the timezone of the plant and the timezone of its customers can differ. When they can differ, it is recommended to put it on 1, otherwise its default value 0 would be okay.', 'N');
execute CreateSystemSetting('WebApplication', 'OVERRULESSTANDARDDELIVERY', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'This setting defines if the user of the WEB stock count application is allowed to select the checkbox colum ''Fixed'' in order to generate a Fixed delivery variation for the entered quantity.', 'N');
execute CreateSystemSetting('WebApplication', 'PASSWORDCOMPLEXITY', '1', 'I', '2', 'N', 'N', 0, 2, '', '0 = No checks on password.'|| chr(10) ||'1 = Minimum length (systemsetting MINPASSWLENGTH) check only'|| chr(10) ||'2 = Use Microsoft Password complexity:'|| chr(10) ||'      - Minimum length of 8 characters'|| chr(10) ||'      - Password contains both upper and lower case characters'|| chr(10) ||'      - Password has at least one digit (numeric character) and one alphanumeric character'|| chr(10) ||'      - Password cannot include (or be equal to) the login name', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWARINFOONWEB', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Only applicable for module financial info on web application. If set to Yes, payments and statements are also shown (mainly applicable for US laundries). When set to N, only invoices are shown (EU laundries).', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWCOUNTDEADLINESTOCUST', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Y means order deadlines and checks will be shown on the Linen Web application and the Linen Assistant Android PDA. '|| chr(10) ||''|| chr(10) ||'N means order deadlines and checks will NOT be avialable on the Linen Web application and the Linen Assistant Android PDA application'|| chr(10) ||''|| chr(10) ||'This has not effect on the visibility in ABSSolute', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWEXPECTEDFULFILLMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This attribute controls whether the expected fullfilment date should be shown after the generation of a garment order via the web portal. Possible values:'|| chr(10) ||' 0 - Do not show the expected fulfillment date (default)'|| chr(10) ||' 1 - Do show the expected fulfillment date. Go to the garment orders tab after creation of the orders'|| chr(10) ||''|| chr(10) ||'The field is only relevant when the module BKLINTERNET is in the license', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWEXPFULLDATE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Show full date', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWFABRIC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the fabric code and description of a product will be displayed in the Wearer Inventory Detail web form when showing the image of he product. Possible values:'|| chr(10) ||'0 = Do not show the fabric information (default)'|| chr(10) ||'1 = Do show the fabric information ', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTFREEOFCHARGE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show free of charge in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTGRADE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show grade in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTISSUEDATE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show issue date in garments screen. (Issue date to current wearer, so last issue date)', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTREPAIRSISSUE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show number of repairs for current wearer (so since last issue date) in garments screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTREPAIRSTOTAL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show total number of repairs in garment screen. ', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTREWASHESISSUE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show number of rewashes for current wearer (so since last issue date) in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTREWASHESTOTAL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show total number of rewashes in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTSTAY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show stay in garments screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTWASHESISSUE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show number of washes for current wearer (so since last issue date) in garments screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTWASHESTOTAL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show total number of washes in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTWEEKSUSEISSUE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show weeks in use by current wearer (so since last issue date) in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWGARMENTWEEKSUSETOTAL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show total weeks in use in garment screen.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWINVOICESONWEB', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Finalized invoices are always shown on the web application.'|| chr(10) ||'1 = Finalized invoices must be released to be shown on the web application.', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWLONGPRODUCTDESC', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Show full product description in web application', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWPRODUCTREMARK', '0', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls whether an extended product remark for a product will be displayed in the Wearer Inventory Detail web form when showing the image of he product. Possible values:'|| chr(10) ||'0 = Do not show the extended product remark (default)'|| chr(10) ||'1 = Do show the extended product remark, if any', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWSUPPLIERPRODUCTCODE', '0', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls whether the supplier product code (as used by the default supplier of the product) should be displayed in the Wearer Inventory Detail web form. This also applies to the product selection control where the supplier product code might be visible as a third column. Possible values:'|| chr(10) ||'0 = Do not show the default supplier product code (default)'|| chr(10) ||'1 = Do show the default supplier product code, if any', 'N');
execute CreateSystemSetting('WebApplication', 'SHOWSUPPLSIZECHART', '0', 'I', '0', 'N', 'N', 0, 3, '', 'This setting controls whether it will be possible to show a PDF document containing a supplier size chart from within the Wearer Inventory Form in the Garment Ordering Web Portal and/or the Wearer Web Portal. This PDF will be stored per supplier. Possible values:'|| chr(10) ||'0 - No supplier size chart can be shown'|| chr(10) ||'1 - A supplier size chart can be shown in the Garment Ordering Web Portal only'|| chr(10) ||'2 - A supplier size chart can be shown in the Wearer Web Portal only'|| chr(10) ||'3 - A supplier size chart can be shown in both Web Portals'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules BKLINTERNET and WEARERWEB are in the license and it affects the behavior for the standard Garment Web Portal as well as the Wearer Web Portal.'|| chr(10) ||'This setting has become obsolete for the restyled web portal released with 9.01.00. Feature no longer supported.', 'Y');
execute CreateSystemSetting('WebApplication', 'SHOWWEBORDERTOTALS', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Yes = print TOTAL column in Web Report Count/Order', 'N');
execute CreateSystemSetting('WebApplication', 'STOCKCOUNTSKIPORDER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if it will be possible to indicate in the stock count / ordering web form if nothing should be ordered. In that case no counts will be done and all ordering products will be set to 0 and marked as fixed so any defined standard delivey quantities will be ignored completely. The internet order will be marked as skipped. Possible values:'|| chr(10) ||'0 = No possiblity to mark internet order as skipped'|| chr(10) ||'1 = It is possible to mark an internet order as skipped', 'N');
execute CreateSystemSetting('WebApplication', 'UHFMONITORSHOWBICONTENT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if a custom version of the UHF buffer details dashboard was created in BI version.'|| chr(10) ||'Only relevant when module UHFBUFFER and module BUSINESSINTELLIGENCE are both licensed.'|| chr(10) ||'When set to Y definition of the following settings is required: '|| chr(10) ||'BISERVERNAME, BISERVERPORT, BIUSERNAME, BIPASSWORD and  BIUHFMONITORDASHBOARDPATH.', 'N');
execute CreateSystemSetting('WebApplication', 'WEARERACCESS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Define the access of web user for wearer menu in web application.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Unlimited (default)'|| chr(10) ||'1= Limited: allow only modifying as long as there are no items in circulation.', 'N');
execute CreateSystemSetting('WebApplication', 'WEARERFUNCTIONWEBPORTAL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether all garments that have been defined for a wearer function should be connected to the wearer when creating a wearer (employment) via the web portal. Possible values: '|| chr(10) ||'0 = all products must be linked to the wearer  (standard)'|| chr(10) ||'1 = wearer can select only products from the function, but not all products are obligated. In the wizard there is a possibility to skip a product.'|| chr(10) ||'2 = wearer can not only select products from the function, but the wearer can even have products outside the function. This is similar to the behavior in the abssolute client.', 'N');
execute CreateSystemSetting('WebApplication', 'WEBACTIVATEREPLACEFLAG', '1', 'I', '1', 'N', 'N', 1, 3, '', 'This system setting is used to default the option of the user during replacement procedure: to activate the replacement automatic flag at the moment of generating the work order for the replacement or at the moment of issuing the new item.'|| chr(10) ||'Possible values: '|| chr(10) ||'     1 = At the moment of replacement'|| chr(10) ||'     2 = At the moment the new item is issued'|| chr(10) ||'     3 = At the moment the item is put into circulation (start rent)', 'N');
execute CreateSystemSetting('WebApplication', 'WEBORDERGRACETIME', '0', 'I', '0', 'Y', 'N', 0, 60, '0;5;10;15;20;25;30;35;40;45;50;55;60', 'Time (in number of minutes) in which the web order is still accepted after the initial deadline has passed. A value 0 means that no grace time is allowed. The allowed maximum grace time will be 1 hour (60 minutes).'|| chr(10) ||''|| chr(10) ||'The value of this setting will be used as a default value in the Stock Count Order Status Control dialog where a new extended dead line can be set for a web order.'|| chr(10) ||''|| chr(10) ||'A defined default grace time that is not a multiple of 5 will be rounded to the next multiple of 5 (e.g 3 ==> 5,  6 ==> 10, 11 ==> 15 etc.) before storing it in the database.'|| chr(10) ||''|| chr(10) ||'Will be used in combination with ALLOWWEBORDERPASTDEADLINE', 'N');
execute CreateSystemSetting('WebApplication', 'WEBPORTALEMAIL', 'info(a)laundry.com', 'S', '', 'N', 'N', null, null, '', 'If in this setting a vallid e-mail address is given, a button will appear in top of the web application to directly send an e-mail to this address.', 'N');
execute CreateSystemSetting('WebApplication', 'WEBPORTALQUITWEARER', '0', 'I', '0', 'N', 'N', 0, 2, '', 'On quit wearer:'|| chr(10) ||'0 = Always disconnect wearer from locker'|| chr(10) ||'1 = Never disconnect wearer from locker'|| chr(10) ||'2 = Have extra option in screen to disconnect wearer from locker.'|| chr(10) ||'Note: with option 0 and 2 the wearer is also disconnected when a future date inactive is entered.', 'N');
execute CreateSystemSetting('WebApplication', 'WEBPRODUCTSMONTHLYUSAGE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This system settings  defines the default value for products field in web report monthly usage.Possible values:'|| chr(10) ||'0= All products (default value)'|| chr(10) ||'1= Budget relevant only. Value 1 is usable only when BUDGETCONTROL module is available and value is NOT set to REALLOCATE or BUDGETCONTROLREALLOCATE module is in the license', 'N');
execute CreateSystemSetting('WebApplication', 'WEBREPORTPREVIEWER', '1', 'I', '1', 'N', 'N', 0, 2, '', 'This setting defines which kind of report viewer will be used to show reports from within the web application. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = PDF preview for all web users '|| chr(10) ||'1 = At web user level is defined if the report preview is done in PDF or advanced preview with export options to XLS, CSV etc.'|| chr(10) ||'2 = Advanced preview for all web users.  '|| chr(10) ||''|| chr(10) ||'This setting is only taken into account when the system setting NEWWEBAPPLICATION is set to Y, otherwise the value of this setting will be ignored and the reports will always be shown as PDF in a preview window.', 'N');
execute CreateSystemSetting('WebApplication', 'WEBRPTCUSTOMERSELECTION', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0 = No customer selection in web reports. The customer is determined at log in.'|| chr(10) ||'1 = Single customer selection in web reports.'|| chr(10) ||'2 = Multiple customer selection in web reports.'|| chr(10) ||'Only customers can be selected to which the webuser has access.', 'N');
execute CreateSystemSetting('WebApplication', 'WEBWORKORDERRESERVATION', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Via this setting it can be controlled if work orders that are created via the web portal should be created in state "Waiting for approval" or "New". The value of this setting will be used as a default value for a setting at customer level. When defined as a default value, the setting at customer level may be changed. When defined as a fixed value, however then it is not allowed to overrule this default value.  In that way, it can be controlled, if the setting should be applied for all customers, or if any exceptions should be made for some customers. Possible values:'|| chr(10) ||'0 - Work orders will be created in state Waiting for approval (default)'|| chr(10) ||'1 - Work orders will be created in state New'|| chr(10) ||'2 - Work orders will be created in state "Supervisor approval needed" (status 3) and the WebX route check in screen is used to approve them'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when the module BKLINTERNET is in the license. By default option 0 will be defined as a default fixed value.', 'N');
execute CreateSystemSetting('Residential Services', 'ACCEPTOTHERCLIENT', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Default value for customer setting (when scanning in per client):'|| chr(10) ||'0 = Do not accept items from another client, they must be scanned in on a delivery note for that client.'|| chr(10) ||'1 = Accept items from another client, they will be returned to the sender (this delivery note)'|| chr(10) ||'2 = Accept items from another client, they will be returned to the owner', 'N');
execute CreateSystemSetting('Residential Services', 'ACCEPTRESPRODUCTS', 'Y', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for customer residential setting:'|| chr(10) ||'Y = Accept all products'|| chr(10) ||'N = Accept only from product list', 'N');
execute CreateSystemSetting('Residential Services', 'ADDUNKNOWNIDCODE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Do not accept unknown ID codes'|| chr(10) ||'1 = Accept unknown ID codes at inscan.'|| chr(10) ||'2 = Accept unknown ID codes at in- and outscan and presort scan.', 'N');
execute CreateSystemSetting('Residential Services', 'ALLOWMODIFYITEMPROPERTIES', '4', 'I', '4', 'N', 'N', 0, 4, '', 'Modify item properties via touchscreen applications:'|| chr(10) ||'0 - Modify not allowed'|| chr(10) ||'1 = Soil Receiving'|| chr(10) ||'2 = Presort scan'|| chr(10) ||'3 = Outscan/Sort'|| chr(10) ||'4 = All', 'N');
execute CreateSystemSetting('Residential Services', 'ALLOWMOVECDN', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 - Not allowed'|| chr(10) ||'1 - Only from unknown client to other'|| chr(10) ||'2 - Between all clients within customer', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHCODEALLOWED', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', 'S', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', 'N', 'N', 1, 26, '', 'All characters that are allowed to be used in the batchcode. For instance, when the batch identification (Batchnumber + Batchcode) is used for a polymark, not all characters are allowed.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHCODEUSAGE', '0', 'I', '0', 'N', 'N', -2, 2, '', 'Use Batchcode as identifier for Batch (in addition to Batchnumber):'|| chr(10) ||'-2 : Batchcode is prefix, length 2 (XX9999)'|| chr(10) ||'-1: Batchcode is prefix, length 1 (X9999)'|| chr(10) ||'0 = Do not use Batchcode (9999)'|| chr(10) ||'1 = Batchcode is suffix, length 1 (9999X)'|| chr(10) ||'2 = Batchcode is suffix, length 2 (9999XX)', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHFORSORTINGSYSTEM', '1', 'I', '1', 'N', 'Y', 1, 9999, '', 'Default batch number for adding client delivery notes via the sorting system.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHMAXWASHES', '0', 'I', '0', 'N', 'N', 0, 9999, '', 'Maximum number of clients (delivery notes) in one batch - 0 means there is no check.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHNRFORLABELS', '0', 'I', '0', 'Y', 'N', 0, 9999, '', '0 = Do not generate delivery notes for labels.'|| chr(10) ||'Other value: first batchnumber used for generating labels. If batch already exists and is closed, the next (+1) number is used. '|| chr(10) ||'Note: when used it is recommended to use a high number, for instance 9990.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHNUMBERING', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Start with Batch number 1 in each new week.'|| chr(10) ||'1 = Continue numbering batches until maximum (9999) is reached, then start with 1 again.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHPICKUP', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1the user must specify the pick up date per customer and batch. The pick up date is used to calculate the delivery date and route.', 'N');
execute CreateSystemSetting('Residential Services', 'BATCHREFRESHRATE', '0', 'I', '0', 'N', 'N', 0, 60, '', 'Refresh rate (in minutes) for automatic refresh of the Batch dialog. 0 means no automatic refresh.', 'N');
execute CreateSystemSetting('Residential Services', 'BOXNUMBERBACKGROUND', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Fill box with:'|| chr(10) ||'0 = Batch color'|| chr(10) ||'1 = Finishing method color', 'N');
execute CreateSystemSetting('Residential Services', 'CDNDELIVERYDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = When closing a batch and the calculated delivery date is less or equal to the closing date the delivery date is set to the first next delivery date for the customer starting from closing date + 1 day (i.e. not including the closing date).'|| chr(10) ||'1 = When closing a batch and the calculated delivery date is less or equal to the closing date the delivery date is set to the first next delivery date for the customer starting from closing date (i.e. including the closing date).', 'N');
execute CreateSystemSetting('Residential Services', 'CHANGEDELIVERYDATE', '0', 'I', '0', 'N', 'N', 0, 3, '', '0 = Delivery date is determined, cannot be changed.'|| chr(10) ||'1 = Allow delivery date to be changed from batch screen'|| chr(10) ||'2 = Allow delivery date to be changed from batch screen and from outscan/sort.  if the user is a system administrator then the date is allowed until six weeks in the past from batch screen.'|| chr(10) ||'3 = Allow delivery date to be changed from batch screen. If the user is a system administrator then the date is allowed until six weeks in the past.', 'N');
execute CreateSystemSetting('Residential Services', 'CHARGERESIDENTIALLABELS', '1', 'I', '1', 'Y', 'N', 0, 5, '', '0 = Never'|| chr(10) ||'1 = Always (default)'|| chr(10) ||'2 = Charge Reprints; Do not Charge New Labels'|| chr(10) ||'3 = Charge Reprints: Charge New Labels Optional'|| chr(10) ||'4 = Do not Charge Reprints: Charge New Labels'|| chr(10) ||'5 = Do not Charge Reprints: Charge New Labels Optional'|| chr(10) ||''|| chr(10) ||'(only for dialogs: OutScanSort, UniqueResidentialItem, ItemsPerClient, SoilReceiving, generate and print labels)', 'N');
execute CreateSystemSetting('Residential Services', 'CHECKONNEWCUSTOMERINBATCH', '0', 'I', '0', 'N', 'N', 0, 1, '', '0=no check'|| chr(10) ||''|| chr(10) ||'1=check if scanned item belongs to a customer that is not yet in the current batch. At inscan this check is done in client selection screen when scanning an ID code. The scan can be accepted or rejected.'|| chr(10) ||'At outscan / Sort an error message is given, it is not possible to add a new customer in the batch.', 'N');
execute CreateSystemSetting('Residential Services', 'CLEARLABELATSOIL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, a button appears in Soil Receiving to clear unused labels. Pressing the button will open a scan dialog to scan the unused labels.', 'N');
execute CreateSystemSetting('Residential Services', 'CLIENTFILTERASSIGNPRODUCT', '1', 'I', '1', 'Y', 'N', 0, 2, '', 'Default value for customer residential setting:'|| chr(10) ||'0 = No Filter'|| chr(10) ||'1 = Filter on Finishing Method'|| chr(10) ||'2 = Filter on Finishing Method per Product', 'N');
execute CreateSystemSetting('Residential Services', 'CLIENTINVOICEDBASEDON', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Default value for configuring if client delivery note are invoiced based on IN or OUT quantities.:'|| chr(10) ||'0 = Based on out / delivered products'|| chr(10) ||'1 = Based on in / received products', 'N');
execute CreateSystemSetting('Residential Services', 'CLIENTLABELLAYOUTCHOICE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Label layout is fixed customer label layout. For reprint the customer label layout is fixed.'|| chr(10) ||'1 = Label layout is default customer label layout. For reprint the customer label layout is set as default, but it is enabled.', 'N');
execute CreateSystemSetting('Residential Services', 'CLIENTSTICKERSPERCUSTOMER', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Print sticker per delivery note'|| chr(10) ||'1 = Print sticker for each item on delivery note', 'N');
execute CreateSystemSetting('Residential Services', 'CLIENTSTICKERSPERFINMETH', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Print sticker per product/fm'|| chr(10) ||'1 = Print sticker for each item', 'Y');
execute CreateSystemSetting('Residential Services', 'CORRECTIONBATCH', '9999', 'I', '9999', 'N', 'N', 1, 9999, '', 'Batch number that is used for adding correction tickets.', 'N');
execute CreateSystemSetting('Residential Services', 'CUSTOMERSTICKERS', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = One sticker per client'|| chr(10) ||'1 = One sticker per delivered piece for which it is configured (in finishing method) that a sticker has to be printed.'|| chr(10) ||'2 = One sticker containing only products / finisihing methods marked for printing on sticker.', 'N');
execute CreateSystemSetting('Residential Services', 'DEFAULTCLIENTNR', '0', 'I', '2', 'N', 'N', 0, 2, '', 'Defines how a new client number is determined.'|| chr(10) ||'0 =  no default'|| chr(10) ||'1 = Display as default the first free number for this customer'|| chr(10) ||'2 = Display as default the highest existing number plus 1', 'N');
execute CreateSystemSetting('Residential Services', 'EMPTYBOXALLOWED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, during outscan and sorting it is possble to empty a box and use it for the same client for the pending garments. A report will be printed containing the box contents and the location.', 'N');
execute CreateSystemSetting('Residential Services', 'EMPTYBOXBEHAVIOR', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting is used in combination with setting EMPTYBOXALLOWED = Yes.'|| chr(10) ||'1 = Empty box button - when a box is full the box must be emptied and a list is printed to be put on the box contents.'|| chr(10) ||'2 = Extra box button - when pressed a new box is added for the same client.', 'N');
execute CreateSystemSetting('Residential Services', 'FILLDEFAULTCOUNTEDOUT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes, the system will automatically copy the value from received to delivered. ', 'N');
execute CreateSystemSetting('Residential Services', 'FINMETHODSTICKERS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'If this setting = 0 then one finmethod sticker is printed per client delivery note , otherwise sum of QtyScannedOut + QtyCountedOut', 'N');
execute CreateSystemSetting('Residential Services', 'INACTIVECLIENTDATES', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Defines the behavior of date inactive and end service'|| chr(10) ||'0 - No relation between dates (default)'|| chr(10) ||'1 - Enddate service calculated based on inactive date. Enddate service not editable.'|| chr(10) ||'2 - Enddate service calculated based on inactive date. Enddate service editable as long as inactive date not filled.', 'N');
execute CreateSystemSetting('Residential Services', 'INACTIVECLIENTDAYS', '0', 'I', '0', 'Y', 'N', 0, 99, '', 'Number of days a client is allowed to deliver wash after end of service date.', 'N');
execute CreateSystemSetting('Residential Services', 'INSCANBULKALLOWED', '1', 'I', '1', 'Y', 'N', 0, 2, '', 'Default value for customer screen:'|| chr(10) ||'0 = No iscan'|| chr(10) ||'1 = Scanned in, in bulk allowed (also per client allowed)'|| chr(10) ||'2 = Scanned in, bulk not allowed (only per client)', 'N');
execute CreateSystemSetting('Residential Services', 'INSCANPERCLIENTSWITCH', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1 it is not allowed to go directly to the next client, the user must always go back to the client selection screen first (in scan per client mode).'|| chr(10) ||''|| chr(10) ||'Set inactive, this systemsetting is not implemented.', 'Y');
execute CreateSystemSetting('Residential Services', 'INVOICEINACTIVECLIENTS', '0', 'I', '6', 'N', 'N', 0, 999, '', 'For performance limit the invoice generation for client invoicing by skipping inactive clients that are inactive for longer than the number of months specified in the value of this setting.'|| chr(10) ||'0 means no restriction.', 'N');
execute CreateSystemSetting('Residential Services', 'MENTIONDELAYANDLATE_OUT', '0', 'I', '0', 'Y', 'N', 0, 3, '', '0 = No message is given during outscan if there are any late or delayed pieces for the customer''s clients'|| chr(10) ||'1 = A message is given when the first item is scanned in a batch if there are any late pieces for the customer''s clients'|| chr(10) ||'2 = A message is given when the first item is scanned in a batch if there are any late and/or delayed pieces for the customer''s clients'|| chr(10) ||'3 = Only at the start of a batch.', 'N');
execute CreateSystemSetting('Residential Services', 'MISSINGPRODUCTSCLIENTMOVE', '0', 'I', '0', 'N', 'N', 0, 4, '', 'This setting is used to control the desired behavior with respect to the validations that should be done when moving a residential client from one customer to another customer. Possible values:'|| chr(10) ||'0 - No checks performed, client is moved'|| chr(10) ||'1 - Check if the product is defined in the Residential PLPC of the destination customer, when a missing product/size/ finishing method is found show a warning'|| chr(10) ||'2 - Check if the product is defined in the Residential PLPC of the destination customer, when a missing product/size/ finishing method is found show an error and the client will not be moved.'|| chr(10) ||'3 - Check if the product is defined in the Residential PLPC or price list of the destination customer, when a missing product/size/ finishing method is found show a warning'|| chr(10) ||'4 - Check if the product is defined in the Residential PLPC or price list of the destination customer, when a missing product/size/ finishing method is found show an error and the client will not be moved', 'N');
execute CreateSystemSetting('Residential Services', 'NEXTDELIVINCLTODAYBEFORE', '0', 'I', '0', 'N', 'N', 0, 23, '', 'This setting is used in the sorting system. Time (in hours) that marks the turning point. When scanned before this time, the next delivery date is determined including today. When scanned after this time then the next delivery date is determined excluding today.', 'N');
execute CreateSystemSetting('Residential Services', 'OUTREGISTRATION', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Customer is scanned / counted / sorted out '|| chr(10) ||'1 = Customer is not scanned / counted / sorted out'|| chr(10) ||'Default / fixed setting for customer screen.', 'N');
execute CreateSystemSetting('Residential Services', 'PRESORTALLOWED', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Default value for customer screen:'|| chr(10) ||'Presort allowed Yes means that clients must be grouped using a presort number. Clients are sorted out using these presort groups.', 'N');
execute CreateSystemSetting('Residential Services', 'PRESORTSIZE', '0', 'I', '0', 'N', 'N', 0, 99, '', 'Maximum number of clients within a presort group. Must be > 0 if presorting groups are used (in combination with customer setting).', 'N');
execute CreateSystemSetting('Residential Services', 'PRINTBATCHCARDS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No batchcards are printed.'|| chr(10) ||'1 = Batch cards are printed per wash process.', 'N');
execute CreateSystemSetting('Residential Services', 'PUBLICSERVICENOVALIDATION', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'Via this setting it can be controlled if it any specific validations should be applied on the public service number as defined for a client resident or private person. In case no specific validations have to be done, the field may be left empty as well.  The validations will be done upon save of the client. Possible values:'|| chr(10) ||'0 - No validations are applicable (default)'|| chr(10) ||'1 - The defined public service number should match the Danish CPR number MOD-11 check', 'N');
execute CreateSystemSetting('Residential Services', 'PWBCOMPCHECKNONUNIQUE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines whether the completeness check dialog should show non-unique products or not.'|| chr(10) ||'Possible values: '|| chr(10) ||'0: Show non-unique products in completeness check dialog(default value)'|| chr(10) ||'1: Do not show non-unique products in completeness check dialog', 'N');
execute CreateSystemSetting('Residential Services', 'PWBDELDATEDETERMNATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting it is used on calculate the client delivery note delivery date.Possible values:'|| chr(10) ||'0 = Delivery date is determined via the residential delivery days(route stops). Moved routes are not taken into account.'|| chr(10) ||'1 = Delivery date is determined via the route schedule and route status control. Moved routes are taken into account. This method should only be used if PWBSCANBYROUTE is set to Yes', 'N');
execute CreateSystemSetting('Residential Services', 'PWBINSCANHOURS', '24', 'I', '24', 'N', 'N', 0, 100, '', 'Number of hours in which a residential item is not allowed to be scanned in again.', 'N');
execute CreateSystemSetting('Residential Services', 'PWBMAXCOMPLETENESSDAYS', '100', 'I', '100', 'N', 'N', 0, 999, '', 'This setting prevents that items that were lost in the plant (or delivered back to the customer without outscan) do not ''muddy the water''. All inscans older then the number of days configured with this setting are discarded in the completeness check. If they are found back and delivered after a couple of weeks, then there is no problem: the only effect will be that the number of pieces expected is not decreased by one. ', 'N');
execute CreateSystemSetting('Residential Services', 'PWBOUTSCANHOURS', '0', 'I', '24', 'N', 'N', 0, 100, '', 'Interval (in hours) after which it is possible to scan out an item again (without being scanned in first).', 'N');
execute CreateSystemSetting('Residential Services', 'PWBROUTECONTROLCREATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if a client delivery note should be linked to a route status control.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Client delivery notes aren’t linked to route control ( default value)'|| chr(10) ||'1 = Client delivery note should be linked to a route control when a CDN is made. If the route control doesn’t exist then it should be created. ( work in combination with PWBSCANBYROUTE=Y) ', 'N');
execute CreateSystemSetting('Residential Services', 'PWBSCANBYROUTE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Scan by route in PWB (Residential services) dialogs.', 'N');
execute CreateSystemSetting('Residential Services', 'RECORDEMPLCLIENTDELNOTE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Employee number not recorded,'|| chr(10) ||'1 = Employee number recorded, not printed on client delivery note,'|| chr(10) ||'2 = Employee number recorded and printed on client delivery note.', 'N');
execute CreateSystemSetting('Residential Services', 'SCONCDNFORLABELS', '0', 'I', '', 'N', 'N', 0, 1, '', '0 = don''t check for CDN having ''labels'' when adding special charges'|| chr(10) ||'1 = on closing a batch, check for every CDN in the batch if a CDN only has ‘labels’.   (so no CDN-lines and no weight). If so, do not add special charges to this CDN', 'N');
execute CreateSystemSetting('Residential Services', 'SHOWDELAYEDCOMPLETCHECK', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes, delayed items will be shown in the completeness check screen.', 'N');
execute CreateSystemSetting('Residential Services', 'SHOWSPECIALSCANSAFTER', '2', 'I', '2', 'N', 'N', 0, 99, '', 'Number of hours after which the special scans are shown in the completeness check of the outscan/sort screen.', 'N');
execute CreateSystemSetting('Residential Services', 'SORTLOGGETGARMENTDATAPWB', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 ONLY Log Errors'|| chr(10) ||'1 Log each transaction, no details.   One row per transaction (per call)  '|| chr(10) ||'2 Log details.'|| chr(10) ||'Remind : to prevent large logs the setting 1 and 2 are only working 1 day (timestamp of this systemsetting)'|| chr(10) ||'the next day this setting is automatically set back to value 0.', 'N');
execute CreateSystemSetting('Residential Services', 'SORTLOGSENDTRACKINFOPWB', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 ONLY Log Errors'|| chr(10) ||'1 Log each transaction, no details.   One row per transaction (per call)  '|| chr(10) ||'2 Log details.'|| chr(10) ||'Remind : to prevent large logs the setting 1 and 2 are only working 1 day (timestamp of this systemsetting)'|| chr(10) ||'the next day this setting is automatically set back to value 0.', 'N');
execute CreateSystemSetting('Residential Services', 'SPECIALCLIENTS', '0', 'I', '0', 'N', 'N', 0, 5, '', '0- No special clients'|| chr(10) ||'1-Pool Client per Customer'|| chr(10) ||'2-Pool Client per Department'|| chr(10) ||'3-Unknown Clients'|| chr(10) ||'4-Unknown and Pool per Customer'|| chr(10) ||'5-Unknown and Pool per Department', 'N');
execute CreateSystemSetting('Residential Services', 'SPECIALSCANSEXPIRATION', '30', 'I', '30', 'N', 'N', 0, 999, '', 'Number of days after which a special scan is expired and will not be shown in the completess check of the Outscan/sort screen', 'N');
execute CreateSystemSetting('Residential Services', 'USEFMPERBATCH', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Do not split batches per finishing method.'|| chr(10) ||'1 = Batches can be scanned out split per finishing method. Only when all finishing methods are closed, the entire batch is closed.'|| chr(10) ||'2 = Sames as 1, but in addition to that it is checked if item is scanned out on a workstation for the correct plant department based on its finishing method. If the the finishing method does not match, then the item will not be accepted.', 'N');
execute CreateSystemSetting('Residential Services', 'USEINTERFACELCTSORT', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'Only used for module INTERFACELCTSORT. This flag indicates whether the interface to the LCT sorting system will be active or not. If set to ‘N’, no data is being exported while scanned out.', 'N');
execute CreateSystemSetting('BNL specific settings', 'CONTRACTCHGMINRVPRC', '0', 'I', '0', 'N', 'N', 0, 100, '', 'Default minimum percentage for residual value calculation in report residual value per wearer products (tailormade, not in standard report).', 'N');
execute CreateSystemSetting('BNL specific settings', 'DETAILEDDELIVERYNOTE', 'N', 'S', 'N', 'Y', 'Y', 1, 1, '', 'Y = print delivery note with subreports'|| chr(10) ||'N = print delivery note without subreports', 'N');
execute CreateSystemSetting('BNL specific settings', 'EMBLEMSTOCK', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'When set to Y all products with type of merchandise 4 (emblems) imported from Axapta will have the flag Record Passive Stock set. ', 'N');
execute CreateSystemSetting('BNL specific settings', 'EXPDIRAVENANCE', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Directory (on server) where the export file for Avenance is created. Add \ at the end.', 'N');
execute CreateSystemSetting('BNL specific settings', 'EXPDIRDOCUWARE', 'C:\ABSSOLUTE\EXP', 'S', 'C:\ABSSOLUTE\EXP', 'N', 'N', null, null, '', 'Directory for export to Docuware.', 'N');
execute CreateSystemSetting('BNL specific settings', 'EXPDIRROTAFORM', 'C:\ABSSOLUTE\EXP', 'S', 'C:\ABSSOLUTE\EXP', 'N', 'N', null, null, '', 'Export directory (on server) where export file for RotaForm is created.', 'N');
execute CreateSystemSetting('BNL specific settings', 'EXPFILENAMEAVENANCE', 'Avenance', 'S', 'Avenance', 'N', 'N', null, null, '', 'Filename of the Avenance export file. The system will automatically add _ddmmyyyy.TXT to make the file unique per date. ', 'N');
execute CreateSystemSetting('BNL specific settings', 'EXPFILENAMEROTAFORM', 'ROTAFORM', 'S', 'ROTAFORM', 'N', 'N', null, null, '', 'Filename for export file to Rotaform (without extension). The system will add _YYYYMMDD_HHMMSS.TXT to it, to make it unique.', 'N');
execute CreateSystemSetting('BNL specific settings', 'IMPDIRARTIKEL', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'Must be a valid directory. This is the directory where the XML-file for importing products from Axapta must be placed.', 'N');
execute CreateSystemSetting('BNL specific settings', 'IMPDIRPAYMENTAXAPTA', 'C:\', 'S', 'C:\', 'Y', 'N', null, null, '', 'Must be a valid directory. This is the directory where the XML-file for importing payment conditions from Axapta must be placed.', 'N');
execute CreateSystemSetting('BNL specific settings', 'LOSTREVENUEPERCAFTER', '50', 'I', '50', 'N', 'N', 0, 100, '', 'Percentage for lost revenue charge calculation, with contract date after 01-06-2003.', 'N');
execute CreateSystemSetting('BNL specific settings', 'LOSTREVENUEPERCBEFORE', '20', 'I', '20', 'N', 'N', 0, 100, '', 'Percentage for lost revenue charge calculation, with contract date before 01-06-2003.', 'N');
execute CreateSystemSetting('BNL specific settings', 'OPTIMAREFRESHRATE', '0', 'I', '0', 'N', 'N', 0, 60, '', 'Refresh rate (in minutes) of the Optima production screen. 0 means no automatic refresh.', 'N');
execute CreateSystemSetting('BNL specific settings', 'RAGAFTERREPLACEMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When a garment needs to be replaced and a replacement work order has been created, then eventually the garment needs to be ragged automatically. This should no longer be done as a separate step in the stockroom. This new functionality in the ''Outscan Sort Batch'' dialog is triggered via the new system setting. Possible values:'|| chr(10) ||'0 - Do not automatically rag garment after creation of replacement workorder'|| chr(10) ||'1 - Automatically rag garment after creation of replacement work order', 'N');
execute CreateSystemSetting('BNL specific settings', 'REPLACEMENTRAGREASON', '-', 'S', '-', 'Y', 'N', 1, 6, '', 'Rag Reason (code) used for replacement procedure in outscan sort batch screen.', 'N');
execute CreateSystemSetting('BNL specific settings', 'REPLACEMENTREASONCODE', '-', 'S', '-', 'Y', 'N', 1, 6, '', 'Reason code used for replacement procedure in outscan sort batch screen.', 'N');
execute CreateSystemSetting('BNL specific settings', 'REPLPRICEIMPORTFACTOR', '1.4', 'F', '1.4', 'Y', 'N', 0, 999, '', 'This factor multiplied with the price from import products from Axapta XML-file gives the replacement price of the imported product that must exists in the general replacement price list.', 'N');
execute CreateSystemSetting('BNL specific settings', 'RESVALUEAFTER', '-', 'S', '- ', 'N', 'N', 1, 6, '', 'Code from residual value schedule used for lost customer residual value calculation garments in circulation, with contract date after 01-06-2003.', 'N');
execute CreateSystemSetting('BNL specific settings', 'RESVALUEBEFORE', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Code from residual value schedule used for lost customer residual value calculation garments in circulation, with contract date before 01-06-2003.', 'N');
execute CreateSystemSetting('BNL specific settings', 'SALESPRICEIMPORTFACTOR', '2.0', 'F', '2.0', 'Y', 'N', 0, 999, '', 'This factor multiplied with the price from import products from Axapta XML-file gives the sales price of the imported product that must exists in the general sales price list. ', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ACTIVETRUCKSONRA', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting determines if all Active trucks will be downloaded to RA. Based on this, a new pop-up for entering the Truck will be available on RA.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ALLOWREMEMBERCREDENTIALS', 'Y', 'B', 'Y', 'N', 'N', 0, 1, '', 'Defines if the system user name and password can be stored. '|| chr(10) ||'When set to N then the Remember Me checkbox will not be visible.'|| chr(10) ||'When set to Y then  the Remember Me checkbox will be visible in the login screen, after the first successful communication. The user can choose to store (remember) the username and password and do not need to be type it again with each log on.'|| chr(10) ||'Note: only applicable to Android platform', 'Y');
execute CreateSystemSetting('Route Assistant PDA', 'AUTOSOILCOUNTOPTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines the relationship between AutoSoil and manual soil counting of a product on the route assistant.'|| chr(10) ||''|| chr(10) ||'0 = Allow soil count on the RA and this overrides the AutoSoil value (default)'|| chr(10) ||'1 = Block soil count on the RA with a message to the user', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'CAPTUREGPSLOCATION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Defines if the route man/driver needs to capture the GPS location for each stop, if not already done.'|| chr(10) ||'0=No'|| chr(10) ||'1=Yes'|| chr(10) ||'2=Yes, GPS location is registered automatically upon Arrival, departure and when registering a stop as undeliverable'|| chr(10) ||''|| chr(10) ||'Only applicable for Route Assistant Android'|| chr(10) ||''|| chr(10) ||'Option 2 is only available as of release 9.04.04', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'CONTACTBLOCKSTOPDEPART', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting defines the default value for the Block Stop Departure flag that can be set for a contact in the Contact Manager dialog. This flag is used to indicate if a contact needs to be changed before departure on a stop is allowed on the RA. Possible values:'|| chr(10) ||'0 = Do not block/not applicable '|| chr(10) ||'1 = Do block departure on stop'|| chr(10) ||'When defined as a fixed default, then the default value cannot be overruled by any user upon creation of a new contact nor may it be changed when modifying it afterwards.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'CONTACTCHECKROUTESTART', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting defines the default value for the Check Before Route Start flag that can be set for a contact in the Contact Manager dialog. This flag is used to indicate if a contact needs to be read before a route is started on the RA. Possible values:'|| chr(10) ||'0 = Do not check/not applicable '|| chr(10) ||'1 = Do check before route starts'|| chr(10) ||'When defined as a fixed default, then the default value cannot be overruled by any user upon creation of a new contact nor may it be changed when modifying it afterwards.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'DWNEMPNONEXTRENTINVLNDDAY', 'Y', 'B', 'Y', 'N', 'N', null, null, 'YN', 'This setting controls if 0-amount non-extended rental invoice lines will be uploaded to Route Assistant on a D-day'|| chr(10) ||''|| chr(10) ||'Y = upload to RA'|| chr(10) ||'N = do not upload to RA', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'GOOGLEMAPSNAVIGATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if Google Maps is used for navigation (requires SIM-card with data plan)'|| chr(10) ||'0=No'|| chr(10) ||'1=Yes'|| chr(10) ||'Only applicable for Route Assistant Android', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INSURANCEMLPREADONLY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Only used in combination with the modules BUDGETPROTECTION and BUTDGETPROTECTIONMLP. This setting can be used to enable or disable MLP (Material Loss Protection) on the route assistant.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INSURANCEMMPREADONLY', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'The controls read only / editable for the MMP insurance field and overrides any other inherited setting from the contract compliancy rule'|| chr(10) ||'Y = read only'|| chr(10) ||'N = editable', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INVOICELINEADJADDRULE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if invoice adjustments can be created in the WebX route check in'|| chr(10) ||''|| chr(10) ||'Only relevant if system setting USEROUTECHECKINSCREEN = Y and INVOICELINEADJAPPROVERULE = 1 (you can only add adjustments if manual approval is enabled)'|| chr(10) ||''|| chr(10) ||'0 = adjustments cannot be added'|| chr(10) ||'1 = new adjustments can be added', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INVOICELINEADJAPPROVERULE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting defines if invoice line adjustments made on the route assistant are allowed to be approved / rejected in WebX route check in'|| chr(10) ||''|| chr(10) ||'System setting USEROUTECHECKINSCREEN must be on Y'|| chr(10) ||''|| chr(10) ||'0 = Default = Automatic approval'|| chr(10) ||'1 = Manual approval in WebX route check in is allowed', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INVOICELINEADJMODIFYRULE', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This defines the type of invoice adjustments that can be modified in the WebX route check in.'|| chr(10) ||''|| chr(10) ||'Only relevant if system setting USEROUTECHECKINSCREEN = Y and INVOICELINEADJAPPROVERULE = 1 (you can only modify adjustments if manual approval is enabled)'|| chr(10) ||''|| chr(10) ||'0 = no adjustments are allowed'|| chr(10) ||'1 = adjustments created in the RA and WebX route check in can be modified'|| chr(10) ||'2 = only adjustments created in WebX route check in can be modified', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INVOICELINEADJNORARULE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if invoice adjustments and settlement is allowed if the Route Assistant has not been uploaded - used when the RA cannot be uploaded or the route was run on paper due to device failure.'|| chr(10) ||''|| chr(10) ||'0 = do not allow invoice line adjustments and settlement'|| chr(10) ||'1 = allow invoice line adjustments and settlement', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'INVOICELINEADJVALUERULE', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This settings defines if invoice line adjustment reject, create and modify are allowed where it increases the overall invoice value'|| chr(10) ||''|| chr(10) ||'Only relevant if system setting USEROUTECHECKINSCREEN = Y and INVOICELINEADJAPPROVERULE = 1'|| chr(10) ||''|| chr(10) ||'0 = No check on invoice value, so increase and decreases in invoice value that was signed for on the RA are allowed'|| chr(10) ||'1 = Creation, modify or rejecting adjustments is only allowed where it DECREASES the invoice value that was signed for on the RA'|| chr(10) ||'2 = Creation or modify adjustments is only allowed where it INCREASES the invoice value that was signed for on the RA - NOTE: this does not affect rejecting transactions, this setting only control add and modify'|| chr(10) ||''|| chr(10) ||'For Value 1 - example, a 701 transaction (a negative adjustment) created on the RA cannot be rejected so it automatically approved as rejecting it would increase the invoice value. So in the route transaction category, this cannot be set as manual approval now.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'MAXWEARERSPDA', '500', 'I', '500', 'N', 'N', 1, 9999, '', 'Maximum number of active wearers that can be exported per customer to the Route Assistant PDA application.'|| chr(10) ||'Maximum for performance reasons.'|| chr(10) ||'If the customer has more active wearers than this value, then none are downloaded', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ONLYPLANTACTIVEPRODUCTSRA', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'Y = Export only products, linked to contracts, set as active on current plant, in plant product settings.'|| chr(10) ||'N = Export all products, linked to contracts, no matter if they are active or not in plant product settings', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ONSITESOILSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Onsite soil scan is registered as an onsite soil scan'|| chr(10) ||'1 = Onsite soil scan is registered as an inscan', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAACCEPTOTHERROUTEDAY', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is used in the PDA Packing Assistant'|| chr(10) ||'0 = Packing notes must be processed per route and day. The user must first select a route and day. Packing notes that don''t belong to this route / day are not accepted.'|| chr(10) ||'1 = The user is allowed to scan a packing note for another route or day. The packing assistant will continue with the new route / day'|| chr(10) ||'2 = When scanning a packing note from another route or day, the packing assistant will show a warning. The user can either reject the scan or continue with the new route and day.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAALLOWCASHPAYMENT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'This setting is used to control if the option to pay invoices via a cash payment is available or not on the PDA upon invoice settlement, When not available, then only the option to pay via check will be visible to the user. Possible values:'|| chr(10) ||'Y = The radio button for cash payment is visible'|| chr(10) ||'N = The radio button for cash payment is not visible. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant for module ROUTEASSSISTANTANDROID.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAALLOWQUITCONTRACT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'This setting defines if the user of the PDA Route Assistant application is allowed to quit contracted customer products. At the laundry the quit transaction has to be approved before it is processed.'|| chr(10) ||'This setting is only relevant for module ROUTEASSSISTANTCONTRACT.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAALLOWTEMPSTOP', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'This setting defines if the user of the PDA Route Assistant application is allowed to define temporary delivery stops for contracted customer products. At the laundry the temporary stop transaction has to be approved before it is processed.'|| chr(10) ||'This setting is only relevant for module ROUTEASSSISTANTCONTRACT.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAAUTOSYNCROUTE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if after finishing a route automatic synchronization should take place.'|| chr(10) ||'This setting is only applicable for Route Assistant Europe and for Route Assistant V2.'|| chr(10) ||'Supported in Route Assistant Android in version 4.0 and up.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAAUTOSYNCSTOP', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if after departure of each stop, automatic synchronization should take place.'|| chr(10) ||'This setting is only applicable for Route Assistant Europe and for Route Assistant V2.'|| chr(10) ||'Supported in Route Assistant Android in version 4.0 and up.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDADELIVERPICKUP', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting is only relevant if setting SETTLEMENTACTIVE set to Y.'|| chr(10) ||'It enables the functionality on the PDA for entering delivery and pick up quantities. '|| chr(10) ||'Is settlement is not active this feature is always enabled.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAEDITDELIVERQTY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if the user is allowed to adjust the delivered quantity on the PDA.'|| chr(10) ||'This setting is only applicable for Route Assistant Europe  and for Route Assistant V2.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAGARMENTORDER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the garment ordering functionality is enabled on the PDA route assistant application. '|| chr(10) ||'System setting is only relevant in case both the garment recording module and the route assistant module'|| chr(10) ||'is installed.'|| chr(10) ||'For Route Assistant Android, also the module ROUTEASSISTANTGARMENT needs to be licensed in order to do garment ordering and scanning with the app.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAINVOICEADJUST', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if the invoice ajdustment functionality is enabled on the PDA route assistant application. '|| chr(10) ||'System setting is only relevant in case both route accounting and the route assistant (US) module'|| chr(10) ||'are installed.'|| chr(10) ||'Not applicable for RouteAssistant Europe.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDANOSIGNATUREBUTTON', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Having a No Signature button. Instead of the signature the Proof of Visit barcode must be scanned.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAPRODUCTSELECT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Selection on product description'|| chr(10) ||'1 = Selection on product code', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDASELECTDRIVINGDATE', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'Allow to overwrite the driving date of the route.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDASETTINGSPASSWORD', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Route Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.'|| chr(10) ||'Note: only applicable to Android platform', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDASYNCINTERVAL', '120', 'I', '120', 'N', 'N', 0, 999, '', 'Defines in minutes the interval for automatic synchronization. Define 0 if no automatic synchronization has to be done.'|| chr(10) ||'This setting is only applicable for Route Assistant Europe and for Route Assistant V2.'|| chr(10) ||'Not supported in Route Assistant Android.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'PDAVOICERECORDING', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if the voice recording button in the Route Assistant PDA application is enabled.'|| chr(10) ||'Setting only relevant if module RouteAssistant and ContactManager are active', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAALLOWFLAGONWEARERMODIFY', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if, on the route assistant, the option to add a flag when changing wearer details is offered.'|| chr(10) ||'If no flag is connected to automatic flag for “Saving changed wearer data” (21)'|| chr(10) ||' then the option is not given regardless of this system setting.'|| chr(10) ||''|| chr(10) ||'0 = default = option not given'|| chr(10) ||'1 = option given if automatic flag for “Saving changed wearer data” (21) is linked to a flag'|| chr(10) ||''|| chr(10) ||'NOTE: this also allows the maintenance of this option in the WebX route check in screen', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAALLOWNOSCANDELIVERY', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting controls whether the No Scan Delivery reason code is available.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAALLOWNOSIGNSETTLEMENT', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if the feature of no signature settlement is allowed on the route assistant settlement screen.'|| chr(10) ||''|| chr(10) ||'0 = default = no button is never visible'|| chr(10) ||'1 = yes, button may be visible (Mobile access template controlled)', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAALLOWWEARERFULLCREDIT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting controls if it is allowed to credit all invoice lines for a wearer at once from within the Invoice lines per wearer screen. This screen is only available on the PDA when system setting RAWEARERINVOICESUMMARY is set to 1. By default it is not allowed to credit these lines at once. Possible values:'|| chr(10) ||'N = A full credit for all wearer invoice lines for a single wearer is not allowed'|| chr(10) ||'Y = It is allowed to do a full credit for all invoice line for a single wearer'|| chr(10) ||''|| chr(10) ||'This setting will be used in combination with RAWEARERINVOICESUMMARY that allows for the display of summarized invoice lines per wearer as well as the possibility to show all individual invoice lines per wearer', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAAUTOUSECODOPENPAYMENT', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'this defines if an open payment for a COD customer is automatically used on the RA settlement screen (so affecting the to pay field) and is then automatically applied during settlement.'|| chr(10) ||''|| chr(10) ||'0 = current behaviour, open payments are not automatically taken into account'|| chr(10) ||'1 = the total to pay and therefore collected amount field is reduced by the amount of any open payments and these payments are applied to the invoice during settlement'|| chr(10) ||''|| chr(10) ||'NOTE: if setting RASHOWTOTALTOPAY = 0 then this setting will not work properly'|| chr(10) ||''|| chr(10) ||'NOTE: this is open payments only, not open credits', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RABLOCKWEARERACTIONS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if the wearer icon/button and scan garments options are available or not in the Stop Actions screen on the RA. Possible values:'|| chr(10) ||'0 - The wearer icon/button and the scan garments icon/button are both available'|| chr(10) ||'1 - Do not show the wearer icon/button, but do show the scan garments icon/button. All wearer related garment scan options are available'|| chr(10) ||'2 - Do not show the wearer icon/button, but do show the scan garments icon/button. Only the Soil and Delivery scan options are available', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RACHANGESRCDRIVINGDATE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'If a route is driven on the Route Assistant on a different date than planned (determined by the arrival date at the first stop) then on upload of the route transaction type 100, the datevalue2 field is used to update the RouteControl.DrivingDate field'|| chr(10) ||''|| chr(10) ||'This setting controls if this update occurs'|| chr(10) ||'0 = update RouteControl.DrivingDate to RouteTransaction.DateValue2'|| chr(10) ||'1 = do not update', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RACONTAINERRECORDING', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if onsite container recording (unload and pick up) is done on site at the customer using the Route Assistant Android App.'|| chr(10) ||'0 = No'|| chr(10) ||'1 = Yes'|| chr(10) ||'This setting only has effect when modules Container Recording and Route Assistant Container are in the license of the plant and system setting ContainerRecordingActive is on Y.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RADATAINTEGRITYCHECKS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if route assistant data loading integrity checks are run.'|| chr(10) ||''|| chr(10) ||'0 = default = no checks'|| chr(10) ||'1 = checks with block'|| chr(10) ||''|| chr(10) ||'If a check fails (see analysis for details), the route will be not sent (if the server side check fails) or deleted (if the RA side check fails) from the route assistant and the driver informed', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAGPSALLOWEDDISTANCE', '0.1', 'F', '0.1', 'N', 'N', 0, 10, '', 'This setting defines the allowed distance between the GPS coordinates of a stop (delivery point) and the actual GPS coordinates of the location where the arrival for this stop was captured on the RA.'|| chr(10) ||''|| chr(10) ||'The allowed distance will be expressed in the length unit that is defined in system setting LENGTHUNIT. A value of 0 implies that no deviation is allowed.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAINVLOCKANDAUTOSETTLE', 'N', 'B', 'N', 'Y', 'N', 0, 1, '', 'This controls the default value and enabled YN for the field ''Lock on Route Assistant'' on maintain invoice dialog for module NEGATIVEMANUALINVOICEFLOW when module AUSCUSTOM is also in the license.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAINVOICELINESORTORDER', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This defines the sort order of the invoices lines on the invoice line screen'|| chr(10) ||'0 = invoice line number ascending'|| chr(10) ||'1 = wearer number ascending then invoice line number ascending, followed by lines with no wearer number in invoice line number ascending order'|| chr(10) ||'2 = locker number ascending then invoice line number ascending, followed by lines with no locker number in invoice line number ascending order'|| chr(10) ||''|| chr(10) ||'NOTE: this only applies when all invoice lines are shown on the RA, so not grouped using system setting RAWEARERINVOICESUMMARY = 1', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAMANDATORYSOILCOUNT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This defines if soil counts on the RA have to be completed before the stop can be departed'|| chr(10) ||'0 = No - so no red ! shown'|| chr(10) ||'1 = Mandatory for all products that are NOT AutoSoil so red * shown if counts have not been entered - 0 counts are allowed.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAPAYMENTCOLLECTIONCONF', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Defines the fixed or default values of field Payment Collection Confirmation in the Route Dialog with values of:'|| chr(10) ||'0 = Single Entry (default)'|| chr(10) ||'1 = Confirmation of entry'|| chr(10) ||'2 = Double Entry'|| chr(10) ||''|| chr(10) ||'This field control how the user of the RA needs to confirm how / if the value they entered for payment collected needs to be confirmed.'|| chr(10) ||'Only visible for SettlementActive = Y and module ROUTEASSISTANT', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAPOVSCANBYPASSALLOWED', 'YN', 'S', 'NN', 'N', 'N', null, null, 'NN;YN;YY;NY', 'This string must contain Y or N characters. '|| chr(10) ||'It controls the values (YN) for the following places on the RA where one can scan a POV barcode. When it is allowed to bypass a POV scan by entering any value, then set it to Y, when one should be forced to enter the correct POV barcode, then set it to N.'|| chr(10) ||''|| chr(10) ||'Allow bypassing a POV scan for a stop - 1st character in string'|| chr(10) ||'Allow bypassing a POV scan for a consumption point - 2nd character in string', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAPRIOFORCREATECUSTPRICEL', '0', 'I', '0', 'N', 'N', 0, 99, '2', 'If a price is added on the route assistant contract management and this means a customer price list is needed, this setting defines the priority for that new list.'|| chr(10) ||''|| chr(10) ||'0 means don''t create a price list'|| chr(10) ||'1 - 99 is the priority used'|| chr(10) ||''|| chr(10) ||'NOTE if the priority value already exists for another price list, the system will add 1 until a free priority is found', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAREPLACELOSSGARMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This defines if the feature for replacing a lost unique item without withdrawing a unique item is available.  So replacement work order and billing for loss without flagging an existing garment as loss.'|| chr(10) ||''|| chr(10) ||'0 = replace loss item button is hidden'|| chr(10) ||'1 = replace loss item button is shown'|| chr(10) ||''|| chr(10) ||'NOTE: this feature will potentially increase circulating inventory above the max inventory', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAREPLACEMENTAUTORETURN', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'If a garment is scanned for replacement on the RA, the old garment is currently flagged for return during the work order process.  This system setting overrides that and the return scan transaction is automatically created and the garment flagged for replacement when the replacement is scanned.'|| chr(10) ||'0 = current functionality (return is flagged during the Work Order process'|| chr(10) ||'1 = garment return scan transaction is automatically created', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASCANTRANSPORTITEMS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is only applicable when setting RACONTAINERRECORDING = 0. '|| chr(10) ||'This for the case only the delivery of transport items, not pickup needs to be recorded.'|| chr(10) ||'Defines if transportation items (containers, carts, bags, boxes etc.)  need to be scanned by the driver as a proof of delivery and a verification if all of them are actually delivered.'|| chr(10) ||'0 = No, scanning of transportation items is not required'|| chr(10) ||'1 = Yes, for all customers'|| chr(10) ||'2 = Only for those customers that require proof of delivery.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASELECTWEARERCPL', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No selection on consumption point when adding a new wearer on the route assistant.'|| chr(10) ||'1 = Selection on consumption point when adding a new wearer on the route assistant.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWACCFORLASTXDAYS', '7', 'I', '7', 'N', 'N', 1, 30, '', 'This setting controls the number of days for which the picked up/returned garments should be shown in the accountability summary for a wearer.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWACCOUNTABILITY', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting controls whether any accountability summaries may be shown in the Select Stop screen for a route as a whole, or from within the View Wearer screen for a specific wearer.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWDELPOINTDESC', '1', 'I', '1', 'N', 'N', 0, 1, '', 'The setting controls if any delivery point information should be shown on a separate line prior to the address info in the Stop Info and Stop Arrival Info screens on the PDA. This setting is only considered, if there is only one active delivery point defined for the customer for the route. Possible values:'|| chr(10) ||'0 = Do not show the delivery point description '|| chr(10) ||'1 = Do show the delivery point description (default)'|| chr(10) ||''|| chr(10) ||'In case there are multiple active delivery points defined for the customer in the route, then the setting is not considered because it is intended to always show the delivery point description in that situation.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWDEPARTMENT', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting controls whether any department inforrmation may be shown in the Select wearer screen for a stop. When enabled, then the department number will be shown together with the wearer number and the wearers will be sorted on department number and wearer number. Otherwise the department number will not be shown and the wearers will be sorted on wearer number.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWGARMENTINFO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls which product info is shown to the driver in the Soil- and Clean Delivery Scan dialogs for Garments.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Product Description and Size (default)'|| chr(10) ||'1 = Product Description, Size and Product Code', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWSELECTSTOPINFO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls which information is presented to the driver in the Select Stop dialog.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Stop # + Customer name (default)'|| chr(10) ||'1 = Customer # + Customer name'|| chr(10) ||'2 = Stop # + Customer # + Customer name', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWTOTALTOPAY', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'control if the total to pay is shown on the settlement screen'|| chr(10) ||'0 = default = do not show'|| chr(10) ||'1 = show field', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWWOFORLASTXDAYS', '30', 'I', '30', 'N', 'N', 1, 90, '', 'This setting controls the number of days the completed work orders should still be shown in the View Garment Order screen for a wearer or the customer as a whole.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RASHOWWORKORDERS', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting controls whether any work may be shown in the View Garment Order screen for a wearer or the customer as a whole.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAWEARERINVOICESUMMARY', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls if all individual invoice lines will be shown when viewing the invoice details, or if a summary will be shown per wearer for those invoice lines that are linked to an individual wearer. Together with these summary lines also all invoice lines will be displayed that are not linked to any individual wearers.'|| chr(10) ||'By default all individual invoice lines will be shown. Possible values:'|| chr(10) ||'1 = Display all individual invoice lines'|| chr(10) ||'2 = Display summary lines per wearer plus all invoice lines that are not linked to an individual wearer '|| chr(10) ||''|| chr(10) ||'This setting can be used in combination with RAALLOWWEARERFULLCREDIT to make it possible to credit a summarized wearer line', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAWEARERSORTORDER', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls how the wearers should be sorted in the Select wearer screen for a stop. By default the sorting will be done on wearer number, but when desired also a sorting on wearer admin number can be done. Possible values:'|| chr(10) ||'1 = Sort by wearer number'|| chr(10) ||'2 = Sort by wearer admin number'|| chr(10) ||''|| chr(10) ||'This setting will be used in combination with RASHOWDEPARTMENT to define the sorting for the Select wearer screen. When this setting is active, then sorting will be done on department number first and within the department either on wearer number or wearer admin number.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'RAZEROPRICEORDERING', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if the route assistant one off ordering process displays products that are set for one off ordering but for this customer, have a zero one off ordering price'|| chr(10) ||''|| chr(10) ||'0 = show all products for one off ordering with no check on price > 0'|| chr(10) ||'1 = show all product for one off ordering that have a price > 0 for this customer'|| chr(10) ||''|| chr(10) ||'NOTE: This is not always the sales price.  Which price is used for one off ordering depends on the product and other settings.  See RA Analysis for details', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'REASONCODEFORTRUCKSALE', '-', 'S', '-', 'N', 'N', null, null, '', 'Reason code used for creating work orders for delivery now from the RA for module FACILITYSERVICE', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ROUTECHECKINFILTER', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Possible values:'|| chr(10) ||'- 0 : No selection on Employee'|| chr(10) ||'- 1 : Selection on Route manager'|| chr(10) ||'- 2 : Selection on District manager', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'ROUTERETURNITEMREDUCTION', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Determines if upload processing of the route processes the garments scanned as returned on the RA or they are just updated as scanned and processed in the RouteReturn dialog.'|| chr(10) ||''|| chr(10) ||'0 = current behaviour (upload processing updates wearer inventory etc)'|| chr(10) ||'1 = garments get a stay of returned but updating of wearer inventory etc is in the route return dialog', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SHOWFUTURECONTACTSONRA', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting controls if contacts with a "new date" greater than the route''s original driving date are loaded to the route assistant'|| chr(10) ||''|| chr(10) ||'0 = No, only contacts with a new date the same or less than the route''s original driving date are loaded'|| chr(10) ||'1 = yes, all contacts regardless of the new date are loaded', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SHOWREMEMBERMECREDENTIALS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Used for the Android Route Assitant application. Defines if the system user name and password can be stored. :'|| chr(10) ||'0 - checkbox for remember me in login screen will not show'|| chr(10) ||'1 - checkbox for remember me in login screen will show. After the first successful communication. The user can choose to store (remember) the username and password and do not need to be type it again with each log on.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SOILCOUNTLOSS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting only works with module SOILCOUNTLOSS and in combination with US soil count (on soil tickets). When set to Yes, it allows to enter the loss soil count. Loss soil count is charged for replacement similar to abuse.', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SOILDEVIATIONOPTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if the check on the route assistant soil count entry based on the value in system setting SOILDEVIATIONPERCENTAGE is a warning or a hard stop'|| chr(10) ||''|| chr(10) ||'0 = default = warning only'|| chr(10) ||'1 = hard stop with an error to the user', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SOILREPORTFORMAT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls which type of layout to use when printing the onsite scan report for a customer. Printing this report will usually be done automatically upon import of a route stop from a PDA. However it is also possible to do a manual reprint from for a route from the Route Status Control dialog. Possible values:'|| chr(10) ||'0 = summary on product level'|| chr(10) ||'1 = summary on product level per wearer', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'SRCPROTECTSAGAINSTONRA', 'NN', 'S', 'NN', 'N', 'N', 2, 2, 'NY', 'This setting will block entry on the route assistant of soil count types if the product on PLPC has SRC setup.'|| chr(10) ||'It is a 2 character setting with the first character being for Loss and the second for Ruin.'|| chr(10) ||'So YY means do not allow soil count loss or soil count ruin to be entered on RA'|| chr(10) ||'Only relevant for module SOILCOUNTLOSS.'|| chr(10) ||'Note: This does not affect client entry on these fields', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'STOPORDERCHANGE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Stop order change not allowed'|| chr(10) ||'1 = Only one time stop order changes allowed'|| chr(10) ||'2 = Permanent and one time stop order changes are allowed.'|| chr(10) ||'This setting is applicable to Route Assistant V2 and Route Assistant Android', 'N');
execute CreateSystemSetting('Route Assistant PDA', 'USEROUTECHECKINSCREEN', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the check-in screen is used.'|| chr(10) ||'When put on Y then transactions created and uploaded by the Route Assistant PDA application will be imported in a staging table which allows the end user to accept or reject transactions.'|| chr(10) ||'When put on N then transactions created and uploaded by the Route Assistant PDA application will be processed immediately.', 'N');
execute CreateSystemSetting('Security', 'ALLOWAUTOLOGIN', 'N', 'B', 'N', 'N', 'Y', null, null, '', 'This field indicates whether it is allowed that a user logs in automatically without supplying a username/password. When the application is started with a command line parameter –U:<user name> and no password is required for the user group, then the login dialog is bypassed. Possible values:'|| chr(10) ||'"Y" - User may login automatically without supplying a password bypassing the Login dialog.'|| chr(10) ||'"N" - User may not login automatically and should always login via the Login dialog.', 'N');
execute CreateSystemSetting('Security', 'CHANGEPASSWORDINMENU', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This field indicates whether menu option "Change password" may be displayed in the File menu of the application. In that way, users are able to change their password directly from within the application. Possible values:'|| chr(10) ||'0 - The option never is visible in the File menu.'|| chr(10) ||'1 - The option is always visible in the File menu.'|| chr(10) ||'2 - Defined on user group', 'N');
execute CreateSystemSetting('Security', 'DEFPASSWORDEXPIRATION', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'This field indicates the number of days before after which a system user password should be changed. Possible values:'|| chr(10) ||'0 - No automatic renewal. User is not forced to change his password. '|| chr(10) ||'1 ..999 - Password should be changed every n days. User will be forced to change his password at login when this period has passed.', 'N');
execute CreateSystemSetting('Security', 'MAXINVALIDPASSWRETRIES', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This field indicates the number of times that a user may try to login with an invalid combination of user/password. Possible values:'|| chr(10) ||'0 - No maximum. User may try to login with an invalid combination of user/password infinitely '|| chr(10) ||'1 ..999 - User may try to login with an invalid combination of user/password n times. After n tries the user will be informed that his account will be locked out.', 'N');
execute CreateSystemSetting('Security', 'MINPASSWORDLENGTH', '0', 'I', '0', 'Y', 'N', 0, 20, '', 'This field indicates the length that a system user password should have at least.  Possible values:'|| chr(10) ||'0 - No check on length of password. '|| chr(10) ||'1 ..20 - Password should have a length of at least n characters', 'N');
execute CreateSystemSetting('Security', 'MULTIPLELOGINALLOWED', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This field indicates whether it must be prevented or not that multiple users login with the same user name. Possible values:'|| chr(10) ||'0 - No check on multiple login'|| chr(10) ||'1 - Always check on multiple login'|| chr(10) ||'2 - Defined on user group. ', 'N');
execute CreateSystemSetting('Security', 'USEPASSWORDCOMPLEXITY', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'This field indicates the complexity that should be used to verify whether a defined system user password is valid. Possible values:'|| chr(10) ||'0 - No checks on password.'|| chr(10) ||'1 - Minimum length (in combination with system setting MINPASSWORDLENGHT.'|| chr(10) ||'2 - Use Microsofts password complexity. Rules for Microsoft complexity:'|| chr(10) ||'- Password is at least 8 characters long,'|| chr(10) ||'- Password has both upper and lowercase characters,'|| chr(10) ||'- Password has at least one number or alphanumerical character,'|| chr(10) ||'- Password cannot include the login name', 'N');
execute CreateSystemSetting('Security', 'WARNPERIODPASSWEXPIRATION', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This field indicates the period in days that the user is warned in advance before an upcoming expiration of its password during login. This value will be used in combination with DEFPASSWORDEXPIRATION. Possible values:'|| chr(10) ||'0 - No warning. User is not warned in advance for an upcoming expiration of its password during login. '|| chr(10) ||'1 ..999 - User will be warned n days in advance for an upcoming expiration of its password during login. He has the possibility to change its password at login.', 'N');
execute CreateSystemSetting('Security', 'WSSYSTEMUSERITERATION', '542', 'I', '542', 'N', 'N', 0, 9999, '', 'The decryption algorithm uses an iteration in order to increase the complexity of decodification.'|| chr(10) ||'This setting is only used for encrypting / decrypting web services.', 'N');
execute CreateSystemSetting('Security', 'WSSYSTEMUSERKEY', 'PBEWithMD5AndDES', 'S', 'PBEWithMD5AndDES', 'N', 'Y', null, null, '', 'Password-based encryption algorithm.'|| chr(10) ||'This setting is only used for encrypting / decrypting web services.', 'N');
execute CreateSystemSetting('Security', 'WSSYSTEMUSERPASSPHRASE', 'Courion', 'S', 'Courion', 'Y', 'N', null, null, '', 'The encyption/decryption algorithm uses this parameter for initialization.', 'N');
execute CreateSystemSetting('Security', 'WSSYSTEMUSERSALT', '0xc7|0x73|0x21|0x8c|0x7e|0xc8|0xee|0x99', 'S', '0xc7|0x73|0x21|0x8c|0x7e|0xc8|0xee|0x99', 'N', 'N', null, null, '', 'The decryption algorithm uses a salt in order to increase the complexity of decodification.'|| chr(10) ||'It should be specified as an array of bytes separated by "|" without any spaces beetwen.'|| chr(10) ||'(for ex: 0xc7|0x73|0x21|0x8c|0x7e|0xc8|0xee|0x99 )'|| chr(10) ||'This setting is only used for encrypting / decrypting web services.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ACTIVATEREPLACEMENTFLAG', '2', 'I', '2', 'N', 'N', 1, 3, '', 'This system setting is used to default the option of the user during replacement procedure: to activate the replacement automatic flag at the moment of generating the work order for the replacement or at the moment of issuing the new item.'|| chr(10) ||'Possible values: '|| chr(10) ||'     1 = At the moment of replacement'|| chr(10) ||'     2 = At the moment the new item is issued'|| chr(10) ||'     3 = At the moment the item is put into circulation (start rent)', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWAUTOCANCELWOINPROGRS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines what work orders can be automatically cancelled when making a wearer, wearer inventory or customer inactive.'|| chr(10) ||''|| chr(10) ||'0 - waiting approval (5) and new (10) (so less than 15) - above this status, we show a message for manual cancellation'|| chr(10) ||''|| chr(10) ||'1 - waiting approval (5), new (10), picked (15), in progress (20), in progress with priority (25)', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWCHANGEINVENTORYSIZE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Change of size only allowed if there are no items in circulation and no work orders in production (not completed and not cancelled).'|| chr(10) ||'1 = Change of size only allowed if there are no work orders in production. When there are items in circulation the size will also be changed for these items.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWEMBLEM', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = All emblemtemplates defined per customer are available. Default the emblemtemplate defined in the wearer function is taken, if the wearer has no function, or the wearer function has no emblemtemplate, then the one from the PLPC is default.'|| chr(10) ||'1 = Only the emblemtemplate defined on the wearerfunction can be selected. If this is empty or wearer has no function then the one from PLPC is taken as default. If this is not defined either it is not possible to add an emblemtemplate.'|| chr(10) ||'2 = Only the emblemtemplate defined on the wearerfunction can be selected. If this is empty or wearer has no function then NULL is taken as default. If this is not defined either it is not possible to add an emblemtemplate.'|| chr(10) ||''|| chr(10) ||'It is is advised to put this setting only on 1 or 2 when system setting USEWEARERFUNCTIONSUBTYPE = N', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWFREECHANGES', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the user is allowed to specify free or charge changes.', 'Y');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWFREEINVENTORY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the user is allowed to specify free or charge inventory.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWMODZEROCHNGPERWEEK', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set to ''N'' the user may not modify the changes per week that are set to 0. This restriction has to be added because a wearer inventory line completely replaced will get changes per week = 0 after the issuing of the first new item. This way rent is not billed double. ', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'ALLOWOVERRIDEDEFAULTGRADE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to override the default grade as determined for a personalized work order line. When allowed, the user has the possibility to define a one-time special grade in the Work order wizard that starts the work order generation process. This special grade will then be applied to all work order lines of the work orders that will be created during the generation process. When no special grade is selected, then the default grades will be determined and used as normal. Possible values:'|| chr(10) ||'0 - Do not allow to override the default grade(s)'|| chr(10) ||'1 - Do allow to override the default grade(s)', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'CHANGESWEEKRELATEDTOMAX', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Defines the relation between Max Inventory and Changed per week'|| chr(10) ||'1=Changes per Week is defaulted by Max Inventory / 2 rounded down.'|| chr(10) ||'2=Changes per Week always equal to Max Inventory'|| chr(10) ||'3=No Relation', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'CHARGEREPLACEDPRODUCT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When the wearer inventory has been replaced with another product/ size, but it is still in use because the new products are not yet in circulation, depending on the System Setting CHARGEREPLACEDPRODUCT(Y/N), the old product could be still invoiced. This situation concerns the wearer inventory with BM1 /ChangesPerWeek and BM3/MaxInventory because these are invoiced based on max inventory/ changes per week and these values are changed when replacing.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'CREATEWORKORDERPERINVENT', 'N', 'B', 'N', 'Y', 'Y', null, null, '', 'if CREATEWORKORDERPERINVENTORY = ''Y'' then a work order must be created for each inventory, i.e. each Work order will contain 1 work order line.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DEFAULTEMBLEMNAME', '0', 'I', '0', 'N', 'N', 0, 3, '', '0=No default'|| chr(10) ||'1=Default the first ''word'' of full name of the wearer'|| chr(10) ||'2=Default the full name of the  wearer'|| chr(10) ||'3=Default the last ''word'' of full name of the wearer', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DEFAULTMULTIBANKLOCKER', '0', 'I', '0', 'Y', 'N', 0, 9999, '', 'Sets a default number of lockers to create for the Multi Locker creation process.  '|| chr(10) ||'If 0, then no defaults are set,'|| chr(10) ||'if > 0, then the starting value for bank defaults to - and number of banks to 1.  The number of lockers to be created will be this value.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DEFAULTMULTILOCKERCREATE', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'Sets defaults for the Multi Locker Creation process.  Note, this take precedence over the DEFAULTMULTIBANKLOCKER system setting'|| chr(10) ||'0 = No defaults'|| chr(10) ||'1 = Default start value to 1 and length to 4', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DEFAULTWEARERNR', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Defines how a new wearer number is generated.'|| chr(10) ||''|| chr(10) ||'0=No default'|| chr(10) ||'1=Display as default the first free number for this customer'|| chr(10) ||'2=Display as default the highest existing number plus 1', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DEFAULTWORKORDERDELFROM', '1', 'I', '1', 'Y', 'N', 1, 2, '', 'System setting used in WorkOrder from ,can have the following values :'|| chr(10) ||'1 - Direct purchase order'|| chr(10) ||'2 - Delivery from stock', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'DISABLELOCKERBANKS', 'N', 'B', 'N', 'N', 'N', 0, 1, '', '0 (N) = banks are enabled for locker creation'|| chr(10) ||'1 (Y) = banks are disabled for locker creation and default to NULL in the database', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'EMBLEMNAMEDEFINITION', '7', 'I', '7', 'Y', 'N', 1, 7, '', 'This setting will be used to control how the emblem name will be filled. '|| chr(10) ||'Possible values:'|| chr(10) ||'1 = First name only'|| chr(10) ||'2 = Last name only'|| chr(10) ||'3 = First name + Last name'|| chr(10) ||'4 = Last name + First name'|| chr(10) ||'5 = First letter First name + Last name'|| chr(10) ||'6 = First name + First letter last name'|| chr(10) ||'7 = manual '|| chr(10) ||'This setting is only relevant when system setting WEARERNAMEDEFINITION = 1', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'LOCKERNUMBERNUMERIC', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 -  Locker allows alphanumeric characters'|| chr(10) ||'1 -  Locker allows numeric only characters', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'MAKECIRC=MAXONCHANGEMAX', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting defines if when max is changed or the wearer inventory is saved, if we try and bring the circulating inventory to the same value as max.'|| chr(10) ||''|| chr(10) ||'For example, if max = 11 and circ = 13 and we reduce max to 9.  If SS = 0 then the system will try and bring circ inline with Max so 4 garments will be flagged for return.  if SS = 1 then 2 garments will be flagged for return'|| chr(10) ||''|| chr(10) ||'0 = bring circ in line with max if max is changed - so the work order or flagged for return is the different in circ and new max'|| chr(10) ||'1 = do not bring circ in line with max - so the work order or flagged for return is the difference in old max and new max', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'MOVEINACTIVEINVENTORY', 'N', 'B', 'N', 'Y', 'Y', null, null, '', 'Y = it is allowed to move inactive wearer inventories to another wearer'|| chr(10) ||'N = it is not allowed to move and inactive wearer inventory (default)', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'MOVEWEARERALLOWEDFLAGS', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'When MOVEWEARERALLOWEDFLAGS = 0, then only show the flags that are set up for the Wearer dialog. When MOVEWEARERALLOWEDFLAGS = 1, then only show the flags that are set up for the Maintain Unique Item dialog. When MOVEWEARERALLOWEDFLAGS = 2, then show flags for both the Wearer dialog and the Maintain Unique Item Dialog.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'MOVEWEARERPRODUCTCHECK', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'When MOVEWEARERPRODUCTCHECK = 0, then the following checks have to be done: '|| chr(10) ||'All combinations must be defined that are attached to the WearerEmployment. When not the case, then show the following message: "The following products / sizes / finishing methods are not defined for customer:" as well as a list of all the missing combinations. '|| chr(10) ||'When MOVEWEARERPRODUCTCHECK = 1, the new checks have to be done:'|| chr(10) ||'Check 1: This check should make sure that all products for the wearer inventory lines of the employment have been defined for the target customer. When not the case, then show the following message: "The following products are not defined for target customer:" and display a list with all missing products.'|| chr(10) ||'Check 2: This check should make sure that all combinations of products and finishing methods have been defined for the target customer. When not the case, then the "Product/Conversion FM"-dialog should be opened where a product and finishing method combination can be selected.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'MOVEWOWITHEMPLOYEMENT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'N= it is not allowed to move wearer employment when there are work orders in progress'|| chr(10) ||'Y= customer could move in progress work order or cancelled them when wearer employment is moved', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'QUITWEARERINVWITHWOINPROG', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if the option to inactivate a wearer or wearer inventory is allowed when there are work orders in progress and not cancelling the work orders.'|| chr(10) ||''|| chr(10) ||'So it allows the scenario where an inactive wearer inventory can have a work order issued against it.'|| chr(10) ||''|| chr(10) ||'0 = do allow (so button "inactive wearer" without cancelling work order is visible)'|| chr(10) ||'1 = do not allow (only option is to cancel the work orders in progress)'|| chr(10) ||''|| chr(10) ||'Which work order status this applies to is controlled by system setting ALLOWAUTOCANCELWOINPROGRS'|| chr(10) ||''|| chr(10) ||'NOTE: this also affects the ability to quit a wearer with work orders in progress on the route assistant.  You can only quit the wearer / inventory if this is status 1', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'REASONCODEFORPLANTLOSS', '-', 'S', '-', 'Y', 'Y', null, null, '', 'This is the reason code used for creating Work orders through Plant Loss. Only available under a custom module; see analysis for details.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'REPLACEWEARERINVSTARTDATE', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'This is used in the replace / renew dialog to control the start date for the wearer inventory if a new one is being created (so either product and or size is being changed)'|| chr(10) ||''|| chr(10) ||'0 = default to same'|| chr(10) ||'1 = default to other and set start date as sysdate', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'SHOWWEARERFILTER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to ''Y'' the user may select a wearer number after selecting the customer in wearer screen.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'SWINGSUITMETHOD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'SWINGSUITMETHOD = 0 is standard swing suit functionality, splitting a delivery in two work orders and invoicing the swing suit in the first week.'|| chr(10) ||'SWINGSUITMETHOD = 1 is invoice swing suit functionality, invoicing the swing suit in the first week, but without splitting the work order. So all items are issued and delivered via one work order.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'TEMPRENTSTOPGRACEPERIOD', '0', 'I', '0', 'N', 'N', 0, 1095, '', 'This setting defines the grace period where it is allowed to scan an item in the laundry to reset a defined temporary rentstop at wearer inventory level. The setting is used to control whether it will be possible to deactivate a temporary rentstop defined at wearer inventory level when scanning an item in the laundry after the defined grace period. When set to 0 no grace period is applicable, which implies that will not be possible to deactivate the rent stop automatically, by scanning an item.This has to be done manually via the Wearer dialog. Possible values:'|| chr(10) ||'0 = No grace period defined'|| chr(10) ||'> 0 = A grace period is defined for n days'|| chr(10) ||'Default value 0.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'USEDEPDAYSINWOREQDATECALC', 'N', 'B', 'N', 'N', 'N', null, null, '', 'During work order creation / modify, the required delivery date is suggested.'|| chr(10) ||''|| chr(10) ||'Y = use department delivery days'|| chr(10) ||'N (default) = use customer delivery days', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERDELETEWHENINACTIVE', '0', 'I', '0', 'N', 'N', 0, 999, '', 'Number of days after which an inactive wearer is deleted. 0 means that the wearer is not automatically deleted, must be deleted manually. This setting is used by the scheduled process clean up wearers.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERINACTIVEWITHNOCIRC', '0', 'I', '0', 'N', 'N', 0, 999, '', 'Number of days after which a wearer with no circulating inventory is set inactive. 0 means that the wearer is not set inactive (must be done manually). This setting is used in the scheduled process clean up wearers.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERINVENTPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if prices will be defined on wearer inventory or wearerfunction level.'|| chr(10) ||'Typical use: in US: Yes, in EU: No.', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERINVPHASEDOUTPRODUCT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to manually create a wearer inventory line for a phased out product. Possible values: '|| chr(10) ||'0 - Do not allow to create a wearer inventory line for a phased out product'|| chr(10) ||'1 - Do allow to create a wearer inventory line for a phased out product after confirmation by the user', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERINVPRICEFROMPLPC', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Used only when wearer inventory price is visible in wearer inventory screen. '|| chr(10) ||'Y = in Add mode, the default wearer inventory price is taken from plpc (defautl value)'|| chr(10) ||'N = in Add mode, wearer inventory price is left empty - no default price. The user has to supply the price in this case. ', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WEARERNAMEDEFINITION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting will be used to control how the user should enter a wearer name. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 - User enters wearer full name. First name, emblem name and search name will be defaulted from full name (default).'|| chr(10) ||'1 - User enters wearer first name and last name as separate fields. Emblem name will be filled based on selected emblem option.'|| chr(10) ||'This setting will be used in combination with system setting EMBLEMNAMEDEFINITION (option 1)', 'N');
execute CreateSystemSetting('Wearer Screen Settings', 'WORKORDERREFERENCE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No value generated'|| chr(10) ||'1 = <customer#><DDMMYY> ', 'N');
execute CreateSystemSetting('Washroom Services', 'DEFCANCELLATIONPERIOD', '182', 'I', '182', 'Y', 'N', 0, 99999, '', 'This setting defines the default cancellationperiod in days, used as a default for the customer screen. This period will be used in combination with the invoicefrequency for the customer (activity).', 'N');
execute CreateSystemSetting('Washroom Services', 'DEFCONTRACTPERIOD', '1095', 'I', '1095', 'Y', 'N', 0, 99999, '', 'This setting defines the default contract period in days, used as a default for the customer screen. This period will be used in combination with the invoicefrequency for the customer (activity).', 'N');
execute CreateSystemSetting('Washroom Services', 'DEFPROLONGATIONPERIOD', '730', 'I', '730', 'Y', 'N', 0, 99999, '', 'This setting defines the default prolongationperiod in days, used as a default for the customer screen. This period will be used in combination with the invoicefrequency for the customer (activity).', 'N');
execute CreateSystemSetting('Washroom Services', 'REASONCODEFORACTIVESTOCK', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when confirming a "Truck Load List" and moving some of the picked goods from passive stock to active stock (enabled via system setting  RECORDPASSIVETRUCKSTOCK)'|| chr(10) ||''|| chr(10) ||'This is only applicable when the module WASHROOM is in the license of the plant.', 'N');
execute CreateSystemSetting('Washroom Services', 'REASONCODEFORTRUCKLOAD', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when confirming a "Truck Load List" and moving the picked goods from stock to the service truck (enabled via system setting  RECORDPASSIVETRUCKSTOCK)'|| chr(10) ||''|| chr(10) ||'This is only applicable when the module WASHROOM is in the license of the plant.', 'N');
execute CreateSystemSetting('Washroom Services', 'REASONCODEMOVETRUCKSTOCK', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when automatically moving the items from one service truck to another service truck. This movement is done for those service trucks that are linked to the source route and target route when moving stops from a route control to another route control.  '|| chr(10) ||''|| chr(10) ||'This is only applicable when the module WASHROOM is in the license of the plant.', 'N');
execute CreateSystemSetting('ORS', 'ADDORSTOEXISTINGPN', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Y, when a soil delivery variation is generated for an ORS product after scanning an OR pack or a pack content, field Add to existing packing note is filled with Y. The delivery variations could be added to existing packing notes with process schedule Add OR Delivery Variations to Existing Packing Notes or processed on generate packing note if not exists a packing note.'|| chr(10) ||'Otherwise field Add to existing packing note is filled with N and the delivery variation is processed on generate packing note.', 'N');
execute CreateSystemSetting('ORS', 'ALLOWCHANGEFMFORPOOL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if the user is allowed to change the finishing method for pool items. This applies to the situation where a user wants to add unique pool items to a delivery note and when adding unique or non-unique pool items to a pack during its assembly in the ORS assembly screen. Possible values:'|| chr(10) ||'0 = Do not allow to scan out or assemble products with a FM different from the ordered product'|| chr(10) ||'1 = Allow to change the FM at outscan or assembly, warning is shown'|| chr(10) ||'2 = Allow to change the FM at outscan or assembly, no warning is shown'|| chr(10) ||'In a multi-read situation the following system setting applies: CHANGEFMFORPOOLMULTIREAD', 'N');
execute CreateSystemSetting('ORS', 'ALLOWDEPOSITSTOCKPOOL', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Possible values:  '|| chr(10) ||'0 = Do not allow deposit stock for unique pool items (default value)'|| chr(10) ||'1 = Only allow deposit stock for unique pool OR content items', 'N');
execute CreateSystemSetting('ORS', 'ALLOWPACKSASCONTENTS', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Define if a pack can be contents of another pack.', 'N');
execute CreateSystemSetting('ORS', 'AUTOFILLASSEMBLEDQTY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Setting used in Assemble Pack dialog on assembling non unique pack contents:'|| chr(10) ||'0 = Non unique pack contents have to be entered and confirmed (standard)'|| chr(10) ||'1 = Non unique pack contents that do not require lot number are filled with default quantity and automatically confirmed.', 'N');
execute CreateSystemSetting('ORS', 'BATCHTOLERANCEPERCENTAGE', '0', 'I', '0', 'N', 'N', 0, 100, '', 'This is the percentage that a cleanroom batch is allowed to exceed its maximum weight by.'|| chr(10) ||'This setting is only relevant when the CLEANROOMBATCHES module is active', 'N');
execute CreateSystemSetting('ORS', 'BATCHTOLERANCERULE', '2', 'I', '2', 'N', 'N', 0, 2, '', 'This defines how the batchtolerancepercentage is applied'|| chr(10) ||'0 = accept going over the batch weight by the tolerance and do not tell the user until the batch weight + tolerance is reached'|| chr(10) ||'1 = accept going over the batch weight by the tolerance and inform the user with a confirm box for each scan or count that overloads the batch into the tolerance percentage'|| chr(10) ||'2 = tolerance not allowed'|| chr(10) ||'This setting is only relevant when the CLEANROOMBATCHES module is active', 'N');
execute CreateSystemSetting('ORS', 'CLEANROOMBATCHCOMPLETION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Possible values:'|| chr(10) ||'0= a cleanroom batch should be washed, dried, folded and then put to out of completete status after print batch card'|| chr(10) ||'1= after print batch card  the next status for a cleanroom batch is out of cleanroom.'|| chr(10) ||'Used only in combination with CLEANROOMBATCHES module.', 'N');
execute CreateSystemSetting('ORS', 'COMPRESSORSLABELCONTENT', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Define the content of ORS labels file'|| chr(10) ||'Possible values:'|| chr(10) ||'0= Each content line will have its own content  information sorted by sequence number.(default value)'|| chr(10) ||'1= content of the the label file will be summed per product size finishing method. If different content lines contain the same product/size/finishing method combination, the system has to export one line instead of each individual line and sum the content quantity of these lines with the same combination. In this case the sorting of the content information in the file must be on alphabetical order descending (no longer on sequence number)'|| chr(10) ||'2=  content of the the label file will be summed  only per product . Size and finishing method are ignored.', 'N');
execute CreateSystemSetting('ORS', 'CRBALLOWCHANGEAFTERCLOSE', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0: not possible to change cart number and machine'|| chr(10) ||'1: it is possible to change cart number and machine', 'N');
execute CreateSystemSetting('ORS', 'CRBDELIVERYNOTEPERBATCH', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 =  CLEANROOMBATCH packing append new batches to open packing notes regardless of batch'|| chr(10) ||'1 = CLEANROOMBATCH packing will create one packing note per batch', 'N');
execute CreateSystemSetting('ORS', 'EXTENDEDSTERILIZATIONFLOW', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Standard flow where the charge is entered after the sterilization run is ready'|| chr(10) ||'1 = Extended flow where the charge is created prior to sterilization run and after that is used confirmed and approved.'|| chr(10) ||'2 = Same as 1 except only for cleanroom charges.', 'N');
execute CreateSystemSetting('ORS', 'MAXPACKALTERNATIVES', '1', 'I', '1', 'Y', 'N', 0, 5, '', 'The maximum number of alternatives that can be defined for a pack contents product.', 'N');
execute CreateSystemSetting('ORS', 'NEXTCARTBUTTONACTION', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, with each pack that is scanned the status of the cart is checked. If the cart is set to ready for sterilization by another scan station, the pack scan is rejected and the user must select the next cart.', 'N');
execute CreateSystemSetting('ORS', 'ORPACKSTERILE', '1', 'I', '1', 'Y', 'Y', 0, 1, '', 'Default vaue for Sterile field.'|| chr(10) ||'0 = Not sterile'|| chr(10) ||'1 = Sterile', 'N');
execute CreateSystemSetting('ORS', 'PACKLABELPRINTING', '0', 'I', '0', 'N', 'N', 0, 2, '', ' If set to value <> 0 all label printing relevant functions in OR Pack Status Control are disabled. Only reprint is possible from the PACK tab-page. Also the text label of the LABEL tab-page will be renamed into Overview.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 =Pack label printing prior to pack assembly and initiated from OR Pack Status Control (default value)'|| chr(10) ||'1 = Pack label printing during pack assembly using the touch screen application. '|| chr(10) ||'2 = Pack label printing after assembly and sterilization initiated from Sterilization Run Status Control.', 'N');
execute CreateSystemSetting('ORS', 'PNLORDEREDQTYEDITABLE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Possible values: '|| chr(10) ||'0 = Order quantity of a packing note line in OR Pack Status Control - Tab page Customer is not editable by the user (default value)'|| chr(10) ||'1= Order quantity of a packing note line in OR Pack Status Control - Tab page Customer is editable by the user'|| chr(10) ||'Note:Please mind that the ordered quantity on packing note line level is a calculated quantity based on delivery variations and standard deliveries. Allowing a user to edit that quantity will lead to intransparency of the ordered quantity.', 'N');
execute CreateSystemSetting('ORS', 'STERILIZATIONF0LOWERLIMIT', '0', 'F', '0', 'Y', 'N', 0, 999, '', 'This system setting defines the lower limit that the F0 value can have when adding a sterilization run.', 'N');
execute CreateSystemSetting('ORS', 'STERILIZATIONF0UPPERLIMIT', '999', 'F', '999', 'Y', 'N', 0, 999, '', 'This system setting defines the maximum limit that the F0 value can have when adding a sterilization run.', 'N');
execute CreateSystemSetting('ORS', 'WASHCYCLENUMBER', '0', 'I', '0', 'N', 'Y', 0, 2, '0;1;2', '0 = no wash cycle number'|| chr(10) ||'1 = wash cycle number is optional'|| chr(10) ||'2 = wash cycle number is mandatory', 'N');
execute CreateSystemSetting('App Settings', 'BPAEXSORTING', '0', 'I', '0', 'N', 'N', 0, 3, '', 'Only used in combination with BPASHOW2STEPPACK = ''Y'':'|| chr(10) ||'0 - Step 1 stop order, step 2 stop order'|| chr(10) ||'1 - step 1 reversed stop order, step 2 stop order'|| chr(10) ||'2 - step 1 stop order, step 2 reversed stop order'|| chr(10) ||'3 - step 1 reversed stop order, step 2 reversed stop order'|| chr(10) ||'Recommended is 2.', 'N');
execute CreateSystemSetting('App Settings', 'BPAGROUPSEQ', '1234', 'S', '1234', 'N', 'N', null, null, '1234', 'This string must contain the characters 1, 2, 3 and 4 only and it controls the order the bulk packing types are shown on the bulk packing assistant'|| chr(10) ||'1 = Customer Logo Mat'|| chr(10) ||'2 = Customer Related Pool'|| chr(10) ||'3 = Bulk Pool'|| chr(10) ||'4 = One way items', 'N');
execute CreateSystemSetting('App Settings', 'BPAPACKBYDEPARTMENT', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls the Bulk packing assistant behaviour for splitting the packing by packing department.'|| chr(10) ||''|| chr(10) ||'0 = Default = no selection of packing department'|| chr(10) ||'1 = Selection of and packing by packing department (sometimes referred to a Plant Department)', 'N');
execute CreateSystemSetting('App Settings', 'BPAPACKBYSTOP', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This control if the bulk packing assistant is packed by stop or group by product for the whole route'|| chr(10) ||'0 = Pack in bulk (default)'|| chr(10) ||'1 = Pack by stop in ascending stop number order'|| chr(10) ||'2 = Pack by stop in descending stop number order', 'N');
execute CreateSystemSetting('App Settings', 'BPASHOW2STEPPACK', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, packing is divided into 2 steps. First step pick the mats from the active stock locations in reversed order, second step is to pack all mats. If the active stock locations are further away it will save time to load the mats on a pallet and bring them to the packing area.', 'N');
execute CreateSystemSetting('App Settings', 'BPASHOWRETURN', '1', 'B', '1', 'N', 'N', null, null, '', 'Defines if the return button is shown on the Bulk Packing Assistant', 'N');
execute CreateSystemSetting('App Settings', 'BPASHOWSTORE', '1', 'B', '1', 'N', 'N', null, null, '', 'Defines if the store button is shown on the Bulk Packing Assistant', 'N');
execute CreateSystemSetting('App Settings', 'BPASORTWITHINGROUP', 'AAAA', 'S', 'AAAA', 'N', 'N', null, null, 'AB', 'String must contain the characters A and B only, 4 times (i.e. AABB, AAAA) and controls the order the bulk packing types are shown within the group on the BPA'|| chr(10) ||''|| chr(10) ||'1st character is for Customer Logo Mats- type 1'|| chr(10) ||'A: Sorted by Priority, Section, Location of active stock location'|| chr(10) ||'B: Sorted by ActiveStockLocation.Section, ASL.Location all ascending'|| chr(10) ||' '|| chr(10) ||'2nd character is for Customer Pool Logo Mats- type 2'|| chr(10) ||'A: Sorted by Priority, Section, Location of ASL'|| chr(10) ||'B: Sorted by ASL.Section, ASL.Location, PlantProductSettings.packingSequence, ProductGroup.code, Product.code, SizeDefinition.code calculated all asc'|| chr(10) ||' '|| chr(10) ||'3rd character is for Pool (Bulk) Products- type 3'|| chr(10) ||'A: Sorted by Priority, Section, Location of ASL'|| chr(10) ||'B: Sorted by PPS.packingSequence, PG.code, Product.code, SD.code calc. all asc'|| chr(10) ||' '|| chr(10) ||'4th character is for One way items- type 4'|| chr(10) ||'A: Sorted by StockRoomLocation.PickingSequence, SRL.RowCode, SRL.LocationCode'|| chr(10) ||'B: Sorted by PPS.packingSequence, PG.code, Product.code, SD.code calc. all asc', 'N');
execute CreateSystemSetting('App Settings', 'BPASTARTLOCATION', '0', 'I', '0', 'N', 'N', 0, 999999999, '', 'defines the ID of the start location of the cells in the hive.  This is the location nearest to the front of the hive and is used to bias the storage algorithm to this location.', 'N');
execute CreateSystemSetting('App Settings', 'BPASTOREFLOW', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No change of location and no location confirmation scan'|| chr(10) ||'1 = Change of location (button), no location confirmation scan'|| chr(10) ||'2 = Mandatory location confirmation scan.', 'N');
execute CreateSystemSetting('App Settings', 'BPASTOREOPTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Defines if the system will suggest and reserve locations when Storing Customer Logo Mats'|| chr(10) ||''|| chr(10) ||'0 = the system will suggest the optimal location and create reservations.'|| chr(10) ||'1 = the user will scan the mat and then scan the wanted location ID. No suggestions or reservation done by the system', 'N');
execute CreateSystemSetting('App Settings', 'CUSTOMERSERVICEEMAIL', '-', 'S', '', 'N', 'N', null, null, '', 'Specific email address of the customer service department of the laundry. '|| chr(10) ||'This is used in the order app.'|| chr(10) ||'This is also used in the oracle TeleService integration data export via email process', 'N');
execute CreateSystemSetting('App Settings', 'CUSTOMERSERVICEPHONE', '-', 'S', '', 'N', 'N', null, null, '', 'Specific phone number from the customer service department of the laundry. This is used in the order app.', 'N');
execute CreateSystemSetting('App Settings', 'DELIVERYPICKUPSCANCHECKFM', 'Y', 'B', 'Y', 'N', 'N', null, null, 'YN', 'Setting used in mobile Bulk Packing Assistant and Route Assistant apps.'|| chr(10) ||'When set to Y, on scanning ID codes for delivery and pick up check for the combination of product, size and finishing method.'|| chr(10) ||'When set to N, on scanning ID codes for delivery and pick up check for the combination of product and size.', 'N');
execute CreateSystemSetting('App Settings', 'ORDERAPPGRACETIME', '5', 'I', '5', 'N', 'N', 0, 240, '', 'Time (in number of minutes) in which the order is still accepted after the deadline is passed. Used in the order app.', 'N');
execute CreateSystemSetting('App Settings', 'ORDERAPPINADVANCEVISITS', '6', 'I', '6', 'N', 'N', 1, 12, '', 'The number of delivery days that are shown in the order app.', 'N');
execute CreateSystemSetting('App Settings', 'PAALLOWEDPARKEDPACKNOTE', 'Y', 'B', 'Y', 'N', 'Y', null, null, '', 'Deternines if the feature to allow a packing note to be parked is available on the packing assistant'|| chr(10) ||'Y = can park'|| chr(10) ||'N = cannot park', 'N');
execute CreateSystemSetting('App Settings', 'PAAMBERWARNINGDEADLINE', '0', 'I', '0', 'N', 'N', 0, 24, '', 'The number of hours before the packing deadline that the packing note time alert is shown in amber'|| chr(10) ||''|| chr(10) ||'0 = default = not used', 'N');
execute CreateSystemSetting('App Settings', 'PADAYTOSHOW', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = default = delivery date shown'|| chr(10) ||'1 = production date shown'|| chr(10) ||' ', 'N');
execute CreateSystemSetting('App Settings', 'PAENTERSHORTCOUNTTYPE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Controls if the packer enters the number of pieces they have packed or the number of pieces they have not packed'|| chr(10) ||''|| chr(10) ||'0 = default = packed pieces entered'|| chr(10) ||'1 = not packed (shorted) pieces entered', 'N');
execute CreateSystemSetting('App Settings', 'PAPACKORDER', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Ascending stop order packing (default)'|| chr(10) ||'1 = Descending order packing', 'N');
execute CreateSystemSetting('App Settings', 'PAPRINTPARKEDSHEET', 'N', 'B', 'N', 'N', 'N', null, null, '', 'defines if a parked packing report is printed when a packing note is parked'|| chr(10) ||'Y = print '|| chr(10) ||'N = do not print ', 'N');
execute CreateSystemSetting('App Settings', 'PAREDWARNINGDEADLINE', '0', 'I', '0', 'N', 'N', 0, 24, '', 'The number of hours before the packing deadline that the packing note time alert is shown in red.'|| chr(10) ||''|| chr(10) ||'0 = default = not used', 'N');
execute CreateSystemSetting('App Settings', 'SETTINGSPASSWORDBPA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Bulk Packing Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.'|| chr(10) ||'Note: only applicable to Android platform. Also, an application reconnect is required in case the system setting is changed.', 'N');
execute CreateSystemSetting('App Settings', 'SETTINGSPASSWORDECA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Exchange Cart Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.'|| chr(10) ||'Note: only applicable to Android platform. Also, an application reconnect is required in case the system setting is changed.', 'N');
execute CreateSystemSetting('App Settings', 'SETTINGSPASSWORDTLA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Truck Load Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.'|| chr(10) ||'Note: only applicable to Android platform. Also, an application reconnect is required in case the system setting is changed.', 'N');
execute CreateSystemSetting('App Settings', 'TLAUNEXPECTEDCONTAINERS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting defines if unexpected containers/ Delivery Notes can be scanned on the Truck Load Assistant app. Unexpected means not linked to the current route.  '|| chr(10) ||''|| chr(10) ||'0 = Unexpected containers/ Delivery Notes are not allowed. '|| chr(10) ||'If they should be delivered with this route, they should be linked to this route via the Truckload Manager screen, before scanning in Truck Load Assistant.'|| chr(10) ||''|| chr(10) ||'1 = Unexpected containers/ Delivery Notes are not allowed unless they belong to a customer that is visited with this route;'|| chr(10) ||''|| chr(10) ||'2 = All Unexpected containers/ Delivery Notes are allowed, regardless of the fact if the customer is visited with this route. If the customer is not visited with this route, the user will be notified. When confirmed a stop for that customer will be added.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDACORRECTIONREASONCODE', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'This setting will be used to configure which reason code should be used when creating a stock correction due to a stock count via the PDA.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDAFORCESTOCKCNTLOCATIONS', '0', 'I', '0', 'Y', 'Y', 0, 999, '', 'This setting will be used to configure the maximum number of stockroom locations that may be subject to a forced stock count when picking the items for a unique pick list via a PDA. A value 0 means that no forced stock counts are intended to be done via the PDA.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDAFORCESTOCKCNTMINMONTHS', '0', 'I', '0', 'Y', 'Y', 0, 60, '', 'This setting will be used to configure the number of months that no stock count has been done to force a stock count when the number of items on stock is below quantity q and the number of months that has passed since the last stock count took place exceeds this defined number of months.  The quantity q can be defined via system setting PDAFORCESTOCKCNTMINQTY. A value 0 means that no forced stock counts are intended based on this combination of settings.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDAFORCESTOCKCNTMINQTY', '0', 'L', '0', 'Y', 'Y', 0, 9999999999, '', 'This setting will be used to configure below which quantity a stock count should be forced in case the stockroom location  has bot been counted within the last n months. The number of months n can be defined via system setting PDAFORCESTOCKCNTMINMONTHS. A value 0 means that no forced stock counts are intended based on this combination of settings.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDAMOVESTOCKREASONCODE', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'This setting will be used to configure which reason code should be used when creating a move stock transaction via the PDA. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDANOSTOCKCOUNTLASTMONTHS', '0', 'I', '0', 'Y', 'Y', 0, 60, '', 'This setting will be used to configure the number of months that no stock count has been done to force a stock count when the number of months that has passed since the last stock count took place exceeds this defined number of months. A value 0 means that no forced stock counts are intended based on this setting.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDAPICKWITHDIFFERENCES', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'This setting will be used to configure whether a pick list line is considered as picked with differences when less items were confirmed picked for a pick list line on the PDA than were requested. Possible values:'|| chr(10) ||'0 - Do not automatically set a pick list line as picked with differences (default)'|| chr(10) ||'1 - Do automatically set a pick list line as picked with differences '|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDARAGFROMSTOCKREASONCODE', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'This setting will be used to configure which reason code should be used when creating a rag from stock transaction due to a stock count via the PDA.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'PDARAGREASONCODE', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'This setting will be used to configure which rag reason (code) should be used when creating a rag from stock transaction due to a stock count via the PDA.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are both in the license and active.'|| chr(10) ||''|| chr(10) ||'This is also used in module UNIQUEITEMSERVICE as the rag reason code for removing a cabinet', 'N');
execute CreateSystemSetting('Picking Assistant PDA', 'SETTINGSPASSWORDPA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Packing Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'ALLOWREMEMBCREDENTIALSLA', 'Y', 'B', 'Y', 'N', 'N', 0, 1, '', 'Defines if the system user name and password can be stored in the Linen Assistant Mobile application'|| chr(10) ||'When set to N then the Remember Me checkbox will not be visible.'|| chr(10) ||'When set to Y then  the Remember Me checkbox will be visible in the login screen, after the first successful communication. The user can choose to store (remember) the username and password and do not need to be type it again with each log on.'|| chr(10) ||'Note1: only applicable to Android platform. '|| chr(10) ||'Note2: from Linen Assistant version 2.10 this setting is moved to the settings screen of the app.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'AUTOCONFIRMWEBORDER', '0', 'I', '0', 'N', 'N', 0, 3, '', '0 = Always manual confirm web orders'|| chr(10) ||'1 = Always automatic confirmation of web orders upon saving the order.'|| chr(10) ||'2 = Manual confirm of web orders, but can be overruled for specific web user.'|| chr(10) ||'3 = Automatic confirmation of web orders, but can be overruled for specific web user.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'DOWNLOADSCANDATEFILTERLA', '0', 'I', '0', 'N', 'N', 0, 99999, '', 'Defines the number of days that the last scan date of a unique item may be in the past in order to be downloaded to the Linen Assistant. Items with a last scan date that is before the current date minus X days are not downloaded. This prevents items that are not seen for a long time from being downloaded, which increases the download and scanning performance.'|| chr(10) ||'When 0 the filter on last scandate is NOT applied.'|| chr(10) ||'Note: this setting applies to the Android version of the Linen Assistant only.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'LASAALLOCATEFUTUREDATES', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'When set to Y (true) then the user can allocate for a future date (max 1 week).'|| chr(10) ||'Allocation until one week in the past is always possible.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'PERLSCRIPTDIR', 'C:\', 'S', 'C:\', 'N', 'N', null, null, '', 'Only used for module PDAPERLINTERFACE, using Perl PDA for stock count.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'PERLSCRIPTNAME', 'script.pl', 'S', 'script.pl', 'N', 'N', null, null, '', 'Only used for module PDAPERLINTERFACE, using the Perl PDA for stock count.', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'PRIMARYORSECONDARYIDLA', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Defines if primary or secondary ID Codes should be transferred to the Linen Assistant mobile application.'|| chr(10) ||'1=Primary ID Codes'|| chr(10) ||'2=Secondary ID Codes', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'SETTINGSPASSWORDLA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Linen Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.'|| chr(10) ||'Note: only applicable to Android platform. Also, an application reconnect is required in case the system setting is changed. ', 'N');
execute CreateSystemSetting('Linen Assistant PDA', 'STOCKCOUNTUPDATEONSITEINV', '1', 'I', '1', 'N', 'N', 0, 1, '', 'Defines if UHF scanning for stock count purposes should update the on-site inventory quantities.'|| chr(10) ||'0=No'|| chr(10) ||'1=Yes', 'N');
execute CreateSystemSetting('Garment Assistant App', 'ALLOWREMEMBCREDENTIALSGA', 'Y', 'B', 'Y', 'N', 'N', 0, 1, '', 'Defines if the system user name and password can be stored in the Garment Assistant Mobile application'|| chr(10) ||'When set to N then the Remember Me checkbox will not be visible.'|| chr(10) ||'When set to Y then  the Remember Me checkbox will be visible in the login screen, after the first successful communication. The user can choose to store (remember) the username and password and do not need to be type it again with each log on.'|| chr(10) ||'Note: only applicable to Android platform', 'N');
execute CreateSystemSetting('Garment Assistant App', 'GASALOCKERFEEDDAYS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This controls the delivery date used to determin the delivery note that unique items to be delivered flagged as to be fed'|| chr(10) ||''|| chr(10) ||'0 = delivery date = system date'|| chr(10) ||'1 = delivery date = system date + 1 when after GASALOCKERFEEDTIME  and = systemdate when before GASALOCKERFEEDTIME (used when they "start feeding tomorrows work before and continue after midnight")', 'N');
execute CreateSystemSetting('Garment Assistant App', 'GASALOCKERFEEDTIME', '00:00', 'S', '', 'N', 'N', null, null, '', 'Used when GASALOCKERFEEDDAYS = 1'|| chr(10) ||'This is the time at which the check changes from DeliveryDate = System date + 1 and Delivery date = System date'|| chr(10) ||'This is used when they "start feeding tomorrows work before and continue after midnight"'|| chr(10) ||''|| chr(10) ||'fixed format of hh:mm  (i.e. 09:00 is 9 oclock in the morning and 14:00 is 2 oclock in the afternoon)', 'N');
execute CreateSystemSetting('Garment Assistant App', 'SETTINGSPASSWORDGA', '123', 'S', '123', 'N', 'N', 3, 15, '', 'Defines the password to access the settings screen of the Garment Assistant App in modify mode.'|| chr(10) ||'For view mode no password is required.'|| chr(10) ||'The password only needs to be entered after the first successful communication with the ABSSolute server, so not after a fresh install.', 'N');
execute CreateSystemSetting('Linen Recording', 'ACCEPTTAREWEIGHTZERO', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'If Y then accept tare weight zero in weighing ticket.'|| chr(10) ||'If N the user is forced to enter a positive tare when zero.'|| chr(10) ||'Note: this setting is also applicable for infinity screens confirm packing and confirm container packing.', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLOWCREDITWEIGHING', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Allow to enter negative lines in ts weighing', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLOWDELVARWITHOUTRQA', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When this system setting is set to N an error should be shown when user try to add a delivery variation without the check that causes a rental quantity adjustement when the current circulating inventory has value 0. ( no record means value 0)', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLOWDNLINESWITHOUTRQA', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When this system setting is set to N a check will be made when a delivery note is finalized.When quantity to be delivered is bigger than 0 and circulating inventory si 0 before finalization and after finalization for mat linen products but not for SER products,DN finalization will not be allowed.', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLOWDUPLICATECPL', 'N', 'B', 'N', 'N', 'N', null, null, 'Y;N', 'If set to Yes, it is allowed to have multiple standard delivery lines overlapping for the same product / size /finishing method / delivery scheme and season.', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLOWMODRENTALQTYADJQTY', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting will be used to configure whether it is allowed to change the quantity of a rental quantity adjustment or not, regardless of the fact whether the adjustment is in the past or the future.'|| chr(10) ||'"N" - It is not allowed to change the quantity of an existing rental quantity adjustment.'|| chr(10) ||'"Y" - It is allowed to change the quantity of an existing rental quantity adjustment.', 'N');
execute CreateSystemSetting('Linen Recording', 'ALLSOILPRODUCTSALLOWED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Y If in soil count entry per consumption point the user is allowed to add all products from the product table (except sales only items and emblems), even if they are not defined in productl ist per customer or in consumption point logistics', 'N');
execute CreateSystemSetting('Linen Recording', 'ALWAYSDELIVERMANUALDV', '1', 'I', '1', 'N', 'N', 0, 1, '', 'This new setting controls if any manual delivery variations (including loans) should always be delivered fully without taking into account any negative delivery variations caused by over deliveries when the module RELATEDLOANBILLING is in the license. Possible values:'|| chr(10) ||'0 = Do take into account any negative delivery variations'|| chr(10) ||'1 = Do not take into account any negative delivery variations', 'N');
execute CreateSystemSetting('Linen Recording', 'AUTOCREATEONSITEINV', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, for products that are marked as order an onsite inventory adjustment is created when confirming an internet order.'|| chr(10) ||'This can only be used when items are not soil counted.', 'N');
execute CreateSystemSetting('Linen Recording', 'AUTOSOILPERC', '0', 'F', '0', 'Y', 'N', 0, 100, '', 'Default setting for the AutoSoil percentage used in customer and contract dialogs', 'N');
execute CreateSystemSetting('Linen Recording', 'BUNDLEROUNDMETHOD', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = round upwards'|| chr(10) ||'1 = if half or more of a bundle remains, then round up, else round down ("5 up 4 down") but not down to zero bundles'|| chr(10) ||'2 = same as option 2 but you can round down to zero bundles', 'N');
execute CreateSystemSetting('Linen Recording', 'CHANGEFMFORPOOLMULTIREAD', '1', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls if the system automatically updates the finishing method for pool items at outscan to the finishing method of that product as ordered at the packingnote. Possible values:'|| chr(10) ||'0 =  the finishing method remains unchanged'|| chr(10) ||'1 =  the finishing method is changed to the ordered finishing method', 'N');
execute CreateSystemSetting('Linen Recording', 'CHECKOVERINVWHENSOIL', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 - the application works as described for the System Setting "SHOWOVERINVENTORYMSG" '|| chr(10) ||'1 - "SHOWOVERINVENTORYMSG" is not taken into account'|| chr(10) ||' and the following checks are done:'|| chr(10) ||'  a. If (CountKeyPad + CountAbused + CountLoss) > Inventory'|| chr(10) ||'    then show error message: "The total soil count can never exceed the inventory." '|| chr(10) ||'  b. If ((CountKeyPad + CountAbused + CountLoss) / Inventory) *'|| chr(10) ||' 100 % >= value from setting SOILDEVIATIONPERCENTAGE then show a warning: "Soil count exceeds the deviation percentage. Are you sure?" with Yes / No buttons.', 'N');
execute CreateSystemSetting('Linen Recording', 'CLEANUPWEEKSNOSOILCOUNT', '26', 'I', '26', 'Y', 'N', 0, 999, '', 'The number of WEEKS of no soil count.'|| chr(10) ||'If a product is set to be soil counted in product list per customer and the product is not soil counted for the number of weeks set via this system setting then a scheduled process will set the product in product list per customer as not needing to be soil counted anymore.', 'N');
execute CreateSystemSetting('Linen Recording', 'CONTAINERSHIPPINGCONFIRM', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No confirmation of delivery date / route'|| chr(10) ||'1 = Confirm delivery date and route (popup dialog).'|| chr(10) ||'This setting is used in the ContainerShippingScan dialog and only in combination with the module LINEN.', 'N');
execute CreateSystemSetting('Linen Recording', 'CORRTICKETONCONSNOTE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set the correction tickets are put on consignment notes as well (including consignment notes made for bulk delivery notes). ', 'Y');
execute CreateSystemSetting('Linen Recording', 'COUNTDAYCANBEINADVANCE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Y/N'|| chr(10) ||''|| chr(10) ||'when Y  then take the first stock count date for the customer, including and starting with today'|| chr(10) ||''|| chr(10) ||'when N  then take the most recent stock count date for the customer where a stock count has not been entered (no record on internetorder or record exists at status 1 for a stock count schedule day) that is older than or equal to today. ', 'N');
execute CreateSystemSetting('Linen Recording', 'COUNTMODE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Saving is done after ''save and processing'' is pressed. As long as the rows are not saved, the entered value overwrites the previous value.'|| chr(10) ||'1 = Saving is done after a value is entered. The value is added to the total column. When entering a new value it is added to the previous. Corrections must be done by entering negative values.'|| chr(10) ||'This setting is applicable both for the soil count and abused columns, both in soil count entry per consumption point and straight even return. It is not applicable for the touchscreen soil count per consumption point. Neither for soil count (based on soil ticket).', 'N');
execute CreateSystemSetting('Linen Recording', 'CPLCOMBINEDTRANSPORT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, it is possible to enter a combined transport number for various distribution points (maximum of 3). These distribution points can be loaded together in one container. The packing notes are printed grouped together.', 'N');
execute CreateSystemSetting('Linen Recording', 'CPLPENDINGDELIVERIES', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes then an extra tab is shown in the consumption point logistics with pending deliveries.', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULTCLEANRETURN', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for the clean return checkbox  in Consumption Point Logistics.', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULTDAYSFORLOAN', '7', 'I', '7', 'Y', 'Y', 0, 999, '', 'The value of this setting determines how many days are added to the delivery date to calculate the default return date for a loan when manually creating a delivery variation. However, this default return date can still be changed into a different date from the user.', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULTDELIVERSTERILE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'default in Consumption Point Logistics', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULTSOILPRODUCTS', '1', 'I', '1', 'N', 'N', 1, 3, '', 'Soil count lines are created in soil count entry per consumption point depending on the value of this system setting:'|| chr(10) ||'1 = products that are defined in consumption point logistic'|| chr(10) ||'2 = products that are defined in product list per customer'|| chr(10) ||'3 = products that are defined in consumption point logistic or exists one active wearer inventory with that soil product and size and wearer belong to selected consumption point logistic'|| chr(10) ||'For all 3 values the products should be set as soil counted in product list per customer.', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULT_PACKINGNOTE_SEL', '3', 'I', '3', 'Y', 'N', 1, 3, '', 'Packing note generation: Default value for the field <Selection on> in Generating Packingnote Form.'|| chr(10) ||'1= Date only, all routes'|| chr(10) ||'2= Route/Depot'|| chr(10) ||'3= Customer'|| chr(10) ||'This setting is also used in the form Cancelling Packing Notes.', 'N');
execute CreateSystemSetting('Linen Recording', 'DEFAULT_PACKINGNOTE_SORT', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Packing note generation: Default value for the field <Sort on> in Generating Packingnote Form.'|| chr(10) ||'1= Route/Stop'|| chr(10) ||'2= Reversed Route/Stop  (actually route/reversed stop)'|| chr(10) ||'3= Customer', 'N');
execute CreateSystemSetting('Linen Recording', 'DELIVERSOILABUSEQUANTITY', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls if automatically any replacement items should be included for next delivery for abused items. Possible values:'|| chr(10) ||'1 = Add abuse counts to delivery variations for next delivery'|| chr(10) ||'2 = Prevent abuse counts from adding to delivery variations for next delivery', 'N');
execute CreateSystemSetting('Linen Recording', 'DELIVERSOILLOSSQUANTITY', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls if automatically any replacement items should be included for next delivery for loss items. Possible values:'|| chr(10) ||'1 = Add loss counts to delivery variations for next delivery'|| chr(10) ||'2 = Prevent loss counts from adding to delivery variations for next delivery', 'N');
execute CreateSystemSetting('Linen Recording', 'DELIVERYAVERAGEDELIVERIES', '1', 'I', '1', 'N', 'N', 1, 99, '', 'Only used for the module AVERAGEDELIVERIES. Determines the number of deliveries over which the average is calculated.', 'N');
execute CreateSystemSetting('Linen Recording', 'DELIVERYSTDHISTORY', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Consumptionpoint Logistics: Defines how changes in delivery/usage standards should be handled.'|| chr(10) ||'1-no historical storage of standards, only store the actual standard.'|| chr(10) ||'2-automatic (when qty changed in the grid, automatically the old quantity is stored)', 'N');
execute CreateSystemSetting('Linen Recording', 'DELIVERYVARIATIONFIXEDQTY', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for fixed quantity on delivery variation. when set to Y, the delivery variation overwrites the standard delivery quantity.', 'N');
execute CreateSystemSetting('Linen Recording', 'DELVARDATEDETERMINATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting it is used on calculate the delivery date of soil count delivery variation after quantities are filled in Soil count entry per consumption point.'|| chr(10) ||'0 = Delivery date is determined via the delivery days(route stops). Moved routes are not taken into account.'|| chr(10) ||'1 = Delivery date is determined via the route schedule and route status control. Moved routes are taken into account. This method should only be used if SCANBYROUTE is set to Yes and ROUTEOBLIGATED is set to Yes, i.e. for each customer route stops are defined.', 'N');
execute CreateSystemSetting('Linen Recording', 'DELVARDELSCHEMEMANDATORY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This system setting controls whether it is mandatory or not to define a delivery scheme when manually creating a delivery variation for a straight-even-return product in the Delivery Variations screen. This delivery scheme is required when confirming the returned quantities in the Straight Even Return screen. Possible values.'|| chr(10) ||'0 = It is optional to define a delivery scheme for an SER product.'|| chr(10) ||'1 = It is mandatory to define a delivery scheme for an SER product.'|| chr(10) ||'The system setting is considered to be on 1 when module ROUTEASSISTANTPDS is active, regardless of its actual value.', 'N');
execute CreateSystemSetting('Linen Recording', 'DELVARFORBUNDLEROUNDING', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'During packing note generation the ordered quantity of a bundle product is rounded up to a whole number of bundles to determine the to-be-delivered quantity .'|| chr(10) ||'This system settting determines if for extra added pieces (negative) delivery variations are created.'|| chr(10) ||'Note: only when at department level the checkbox use bundles is checked bundle rounding is done.', 'N');
execute CreateSystemSetting('Linen Recording', 'DELVARPACKINGDEPTCHECK', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether a warning or error-message should be given in the Delivery Variations dialog when a consumption point is selected that is linked to a packing department that belongs to a different plant than the plant of the current business unit. Possible values:'|| chr(10) ||'0 = Do not give a warning'|| chr(10) ||'1 = Do give a warning'|| chr(10) ||'2 = Do raise an error-message', 'N');
execute CreateSystemSetting('Linen Recording', 'FIXEDBILLPERCENTAGE', '100', 'I', '100', 'Y', 'N', 0, 100, '', 'Used for the module Fixed Delivery and Billing. System setting is used as a default for the bill percentage in the Consumption point logistics dialog.', 'N');
execute CreateSystemSetting('Linen Recording', 'FIXEDDELBILLBUFFERPERIOD', '0', 'I', '0', 'N', 'N', 0, 14, '', 'This setting contains the buffer period in days that should be taken into account when calculating the total circulating inventory for a given date.'|| chr(10) ||'It will be used from within the scheduled process to recalculate the delivery and billing quantities at CPL level as a fixed percentage of the circulating inventory. Only the rental qty adjustments will be taken into account that have an adjustment date <= calculation date + buffer period.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the FIXEDDELIVERYANDBILLING module is in the license', 'N');
execute CreateSystemSetting('Linen Recording', 'FIXEDDELIVERYPERCENTAGE', '50', 'I', '50', 'Y', 'N', 1, 100, '', 'Used for the module Fixed Delivery and Billing. System setting is used as a default for the delivery percentage in the Consumption point logistics dialog.', 'N');
execute CreateSystemSetting('Linen Recording', 'FREEOFCHARGECPL', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls if free-of-charge quantities will be used per invoice frequency or invoice, or for a fixed period (e.g. yearly). Possible values:'|| chr(10) ||'1 = Use free-of-charge quantities per invoice or per invoice frequency'|| chr(10) ||'2 = Use fixed free-of-charge contract quanties per period'|| chr(10) ||'Setting is only relevant when system setting FREEOFCHARGEINCPLPERDATE = Y and only in combination with periodical invoicing, so not for direct invoicing', 'N');
execute CreateSystemSetting('Linen Recording', 'FREEOFCHARGEINCPLPERDATE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set, it is possible to define free of charge quantity in cpl with a start date, in the same way as rental quantity adjustments are now defined in the application. In this case the free of charge quantity from plpc is just a redisplay field', 'N');
execute CreateSystemSetting('Linen Recording', 'HANDLINGOFREJECTS', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = regular delivery'|| chr(10) ||'1 = Own delivery note'|| chr(10) ||'Default value 0.'|| chr(10) ||'0 means that a delivery variation is created, which is then added on the generated packingnote. With option 1 a specific PN is created.'|| chr(10) ||'Only used in Soil Count Infinity.'|| chr(10) ||'NOT USED', 'Y');
execute CreateSystemSetting('Linen Recording', 'LABELSFORMULTIREADISSUE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if any labels should be printed upon issue of unique pool items in case of multi-read issue. Possible values:'|| chr(10) ||'0 = Do print labels'|| chr(10) ||'1 = Do not print labels', 'N');
execute CreateSystemSetting('Linen Recording', 'LOADOPTIMIZERSPLITRULE', '1', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls if the remainder products that do not completely fill a cart may be split over multiple mixed carts or not. This is in fact the main difference between the old straightforward load optimizer functionality when compared to the current more flexible mechanism (apart from the distinction between base products and supplementary products as well as the use of a volume factor and maximum fill percentage for base products per transport article). Possible values:'|| chr(10) ||'0 - Do not split remainder products over multiple mixed carts'|| chr(10) ||'1 - Do try to split remainder products over mixed carts'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the LOADOPTIMIZER module is active.', 'N');
execute CreateSystemSetting('Linen Recording', 'MAXORDERQTYWEBPDA', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if a maximum number of items to be ordered can be defined at CPL level. This maximum (if any) will be taken into account when ordering items via a PDA or via the Web Portal.'|| chr(10) ||'Possible values'|| chr(10) ||'0 = No maximum. application behaves like before'|| chr(10) ||'1 = Maximum can be defined on product level, PLPC level or CPL level'|| chr(10) ||'2 = Defined on customer level if any maximum can be defined', 'N');
execute CreateSystemSetting('Linen Recording', 'MPDNHIDEBUTTONS ', '-', 'S', '-', 'N', 'N', 1, 4, '4', 'NOT USED', 'Y');
execute CreateSystemSetting('Linen Recording', 'NODELIVERYOFREJECTS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if any items that are recorded as rejected by the customer at soil count will be delivered automatically to the customer as free of charge items at the next delivery or not. Possible values:'|| chr(10) ||'0 = Do add the rejected items as free of charge items to the next delivery'|| chr(10) ||'1 = Do not add any rejected items as free of charge items to the next delivery'|| chr(10) ||'Default value 0.'|| chr(10) ||'In either case delivery variations will be created, but when set to 1 these variations will be immediately marked as processed so they will be ignored when generating packing notes', 'N');
execute CreateSystemSetting('Linen Recording', 'ORDERSTATUSREFRESH', '5', 'I', '5', 'N', 'N', 0, 60, '', 'Setting for the automatic refresh interval for stockcountorderstatuscontrol form,defined in minutes.'|| chr(10) ||'0 means no automatic refresh.', 'N');
execute CreateSystemSetting('Linen Recording', 'ORDERSTATUSSHOWSOILED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes then Show Soiled Counts in Stock Count Order Status', 'N');
execute CreateSystemSetting('Linen Recording', 'OVERFREEQTYWARNING', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to yes then a warning is given during entry of delivery variations in case the quantity entered causes that the total quantity to be delivered for that week exceeds the free of charge quantity defined for that product/size/finishingmethod in productlist per customer. If free of charge is 0 then this warning is never given.', 'N');
execute CreateSystemSetting('Linen Recording', 'OVERUSECONTRACTRENEWAL', '0', 'I', '0', 'N', 'N', 0, 999, '', 'This setting defines the period in days before the FOC contract expires where a new FOC contract should be created automatically.  A value 0 means no automatic prolongation. Possible values:  0..999'|| chr(10) ||''|| chr(10) ||'Setting is only relevant when system setting FREEOFCHARGEINCPLPERDATE = Y', 'N');
execute CreateSystemSetting('Linen Recording', 'OVERUSENOTIFICATION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting defines if a a notification should be send to the customer service employee when overuse occurrs, or is about to occur. Possible values:'|| chr(10) ||'0 = No notification'|| chr(10) ||'1 = Send notification upon overuse'|| chr(10) ||'2 = Send notification before overuse occurs (based on system setting OVERUSENOTIFICATIONLIMIT)'|| chr(10) ||'Setting is only relevant when system setting FREEOFCHARGEINCPLPERDATE = Y', 'N');
execute CreateSystemSetting('Linen Recording', 'OVERUSENOTIFICATIONLIMIT', '0', 'I', '0', 'N', 'N', 0, 100, '', 'This setting defines the number of items that may be delivered to a customer free-of-charge as a percentage. As soon as thius number has been reached, the customer should be notified. Possible values:  0..100'|| chr(10) ||''|| chr(10) ||'Setting is only relevant when system setting FREEOFCHARGEINCPLPERDATE = Y and system setting OVERUSENOTIFICATION <> 0', 'N');
execute CreateSystemSetting('Linen Recording', 'PACKINGNOTECOLUMNS', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Based on this system setting the layout of packing note report will show or not the bundle information.'|| chr(10) ||'Possible values:'|| chr(10) ||'1 = Show columns: Norm    Variation    Ordered     To-Deliver'|| chr(10) ||'2 = Show columns: Ordered    Bundle Qty     #Bundles     #Pieces', 'N');
execute CreateSystemSetting('Linen Recording', 'POOLITEMSLOSTINPLANTDAYS', '0', 'I', '0', 'N', 'N', 0, 9999, '', 'For pool items that are in the plant, this setting defines how many days after inscan, they are marked as lost in the plant.'|| chr(10) ||'Value 0 means that this feature is not active. Only when not zero the related scheduled processes are available.', 'N');
execute CreateSystemSetting('Linen Recording', 'PRINTPACKERS', '1', 'I', '1', 'Y', 'N', 1, 3, '1', '1 = only print packing notes (default)'|| chr(10) ||'2 = only print packers. Packingnote is generated but not printed. Packers are only printed if there is at least one packingnoteline with putuptype = 5.'|| chr(10) ||'3 = print both packers and packing notes. Packingnote is always printed, packers are printed if there is at least one product with Putuptype = 5.', 'N');
execute CreateSystemSetting('Linen Recording', 'RECORDCUSTOMERCOUNTS', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting affects the available functionality within the  "Soil Count Entry per Consumption Point" screen. When this setting is set to "Y", then the user has the possibility to register the number of items that has been reported as picked up from the customer at the last delivery in a pair of columns similar to the "Abused" columns. When set to "N", then this pair of columns will not be visible at all.'|| chr(10) ||'This registered number of counted items will not be taken into account for any next delivery and will therefore not result in a delivery variation of any type when completing the soil count.'|| chr(10) ||' '|| chr(10) ||'It is not applicable for the touchscreen application for soil count per consumption point.', 'N');
execute CreateSystemSetting('Linen Recording', 'RECORDCUSTOMERREJECTS', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting affects the available functionality within the  "Soil Count Entry per Consumption Point" screen. When set to "Y", then the user has the possibility to register the number of items that has been reported as rejected from the customer at the last delivery in a pair of columns similar to the "Abused" columns. When set to "N", then this pair of columns will not be visible at all.'|| chr(10) ||'This registered number of rejected items should be taken into account for the next delivery and will therefore result in a delivery variation with type "Soilcount" and subtype "Rejected" when completing the soil count.'|| chr(10) ||' '|| chr(10) ||'It is not applicable for the touchscreen application for soil count per consumption point.', 'N');
execute CreateSystemSetting('Linen Recording', 'RECORDCUSTOMERSHORTAGES', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting affects the available functionality within the  "Soil Count Entry per Consumption Point" screen. When set to "Y", then the user has the possibility to register shortages that have been reported from the customer at the last delivery in a pair of columns similar to the "Abused" columns. When set to "N", then this pair of columns will not be visible at all.'|| chr(10) ||'This registered shortage should be taken into account for the next delivery and will therefore result in a delivery variation with type "Soilcount" and subtype "Shortage" when completing the soil count.'|| chr(10) ||' '|| chr(10) ||'It is not applicable for the touchscreen application for soil count per consumption point.', 'N');
execute CreateSystemSetting('Linen Recording', 'RENTBUSINESSUNIT', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No check on rent business unit'|| chr(10) ||'1 = Show warning if the business unit does not match the rent business unit.'|| chr(10) ||'2 = Show an error message if the business unit does not match the rent business unit', 'N');
execute CreateSystemSetting('Linen Recording', 'REPLENISHDELCANBETODAY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Y/N'|| chr(10) ||'If Yes,  '|| chr(10) ||'       if Pack On Count Day = YES,  replenishment date can be today'|| chr(10) ||'       if Pack on Count Day = NO, next deliverydate will be taken'|| chr(10) ||''|| chr(10) ||'if No, replenishment date = today + 7 days', 'N');
execute CreateSystemSetting('Linen Recording', 'REPLENISHMENTCOMPULSORY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, in the stock count / replenishment schedule days can be marked as compulsory. These will be marked in the stock count order status and in the web portal.', 'N');
execute CreateSystemSetting('Linen Recording', 'ROUTELISTPRINTALLDELNOTES', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set all packing note numbers are printed on Route List.'|| chr(10) ||'When not set the packing notes for bulk put up items are excluded from printing when these items should not appear on a packing note.', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWALLINOUTSCANSORTBATCH', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Y = Delivery variations with origin other than ''Soil Count'' are visible in and can be processed from the Outscan Sort Batch dialog.'|| chr(10) ||'N = Only delivery variations with origin ''Soil Count'' are visible in and can be processed from the Outscan Sort Batch dialog.', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWAVGDELQTY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Delivery Variations screen: When set to Y an extra column is is available in the grid showing the average delivered quantity over the past 24 weeks. ', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWDELVARBILLINGMETHOD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the billing method should be shown in the delivery variations dialog (in the grid as well as the detail dialog). Possible values:'|| chr(10) ||'0 - Do not show the billing method (default)'|| chr(10) ||'1 - Do show the billing method'|| chr(10) ||''|| chr(10) ||'By default, the billing method is not displayed.', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWLASTDELINDELVARIATION', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting controls whether the last delivery date and delivered quantity for a product, size, finishing method combination should be displayed in the delivery variations dialog in Add mode.'|| chr(10) ||'N = Do not display the last delivery date and quantity upon Add'|| chr(10) ||'Y = Do display the last delivery date and quantity upon Add', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWMINMAXSTOCKQTY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Only used in combination with module AVERAGEBASEDNORMSTOCK. When set to Yes'|| chr(10) ||', the minimum and maximum stock quantity can be specified.', 'N');
execute CreateSystemSetting('Linen Recording', 'SHOWOVERINVENTORYMSG', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Soil Entry: Set when check on inventory has to be performed in soil count entry screen. When this check is performed and the inventory is less than the soil counted pieces a warning message is given to the user.', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILCOUNTCHECKACTIVECPL', '0', 'I', '0', 'N', 'N', -2, 99, '', '0 : No check on active CPL.'|| chr(10) ||'-1 : Only products that are active in the CPL or that are not at all defined in the CPL or that have an outstanding circulating inventory are shown in the soil count screen.'|| chr(10) ||'-2 : Only products that are active in the CPL or that are not at all defined in the CPL or that have an outstanding onsite inventory are shown in the soil count screen. Note that this works only in combination with onsite inventory registration.'|| chr(10) ||'> 0 : Only products that are active in the CPL, and after they expire they are still shown for a number of days, or that are not at all defined in the CPL.'|| chr(10) ||'Note: Use the systemsetting DEFAULTSOILPRODUCTS set to 1 to filter out the products that are not defined in the CPL.', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILCOUNTCHECKDELSCHEME', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = No check on delivery week'|| chr(10) ||'1 = Check on soil count date in delivery week as defined in CPL.', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILCOUNTCIRC', '1', 'I', '1', 'N', 'N', 0, 2, '', '0 = Circulating inventory is not visible in Soil Count Entry per Consumption point'|| chr(10) ||'1 = Circulating inventory is visible in Soil Count Entry per Consumption point when it is invoiced (Billing method 3 Circulating inventory)'|| chr(10) ||'2 = Circulating Inventory is always visible in Soil Count Entry per Consumption point', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILCOUNTSELECTION', '1', 'I', '1', 'Y', 'Y', 1, 4, '', 'Soil Entry: Used as default selection for a soil ticket in soil entry screen. '|| chr(10) ||'Possible values:'|| chr(10) ||'1=Stop '|| chr(10) ||'2=Soil ticket '|| chr(10) ||'3=Invoice '|| chr(10) ||'4=Customer', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILDEVIATIONPERCENTAGE', '30', 'F', '30', 'Y', 'N', 0, 100, '', 'Default deviation percentage for Soil Reasonability Report.'|| chr(10) ||'Also used for warning or blocking high soil counts on the Route Assistant'|| chr(10) ||'if this is warn or block is determined by system setting SOILDEVIATIONOPTIONS', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILDEVIATIONSOILPERCNEG', '10', 'F', '10', 'Y', 'N', 1, 100, '', 'Used to check the maximum deviation for Scrutiny BELOW average', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILDEVIATIONSOILPERCPOS', '50', 'F', '50', 'Y', 'N', 1, 100, '', 'Used to check the maximum deviation for Scrutiny ABOVE average', 'N');
execute CreateSystemSetting('Linen Recording', 'SOILWEEKSFORAVERAGE', '13', 'I', '13', 'Y', 'N', 2, 13, '', 'Default number of weeks for calculating the average soil quantity, for the Soil Reasonability Report.'|| chr(10) ||' ', 'N');
execute CreateSystemSetting('Linen Recording', 'SPREADLARGESTOCKCOUNTDV', '0', 'I', '0', 'N', 'N', 0, 100, '', 'If 0 (default), no action'|| chr(10) ||''|| chr(10) ||'If greater than zero then take this as the percentage of the standard quantity on the replenishment day that if the DV to be created exceeds, it gets split over 2 days.'|| chr(10) ||'i.e. 50 means if the amount to be delivered exceeds 50% of the delivery days standard value, split the delivery over 2 days'|| chr(10) ||''|| chr(10) ||'Only implemented for ABSSolute stock county entry, not web based entry', 'N');
execute CreateSystemSetting('Linen Recording', 'STOCKCOUNTPROCESSING', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = All stock counts/orders per customer are processed'|| chr(10) ||'1 = Only the stock counts/orders from the customer and date are processed.', 'N');
execute CreateSystemSetting('Linen Recording', 'THEOWEIGHTCOMPARISON', '10', 'F', '10', 'N', 'N', 0, 100, '', 'This setting is only used in the container shipping scan screen. The value is the percentage of deviation between the real weight and the calculated weight. If the deviation is bigger than this value, the scan must be confirmed by an authorized person.', 'N');
execute CreateSystemSetting('Linen Recording', 'UNIQUEBUNDLEEXPDAYS', '0', 'I', '90', 'N', 'Y', 0, 999, '', 'Defines number of days since the creation of a bundle until the bundle expires', 'N');
execute CreateSystemSetting('Linen Recording', 'UNIQUEBUNDLEFIXEDQUANTITY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Module UniqueBundles - This setting determines whether the contents of a uniquelycoded bundle can be changed manually, or is fixed.', 'N');
execute CreateSystemSetting('Linen Recording', 'UNIQUEBUNDLESINGLEPRODUCT', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Allows to change the default bundle quantity to 1.'|| chr(10) ||'1= Default and as currently standard'|| chr(10) ||'2= Unique Bundle Value may be equal to = 1', 'N');
execute CreateSystemSetting('Linen Recording', 'USEBUFFERCONTNRFORBUNDLES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines if recording of bundles into buffer containers is in use or not.'|| chr(10) ||'0 = Not in use, bundles can be scanned on a packing note without being scanned to a buffer container'|| chr(10) ||'1 = Only bundles linked to a buffer container can be scanned on a packingnote.', 'N');
execute CreateSystemSetting('Linen Recording', 'WEBMAXORDERWARNING', '1', 'I', '1', 'N', 'Y', 1, 2, '', 'This attribute controls whether a warning or a (blocking) error message should be shown to the web user when he wants to confirm an order via the web or the Order App and the ordered quantity for a product exceeds the defined maximum quantity. Possible values:'|| chr(10) ||'1 = Show warning but still allow confirmation of the order (default)'|| chr(10) ||'2 = Show error-message'|| chr(10) ||'Only relevant when the module LVMINTERNET or ORDERAPP is in the license.', 'N');
execute CreateSystemSetting('Linen Recording', 'WEBWKSAVERAGEDELIVERY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This attribute controls how the average delivery for the last 4 weeks should be calculated. Possible options:'|| chr(10) ||'0 = Calculate the average number of delivered items per week (default)'|| chr(10) ||'Take the total number of items that has been delivered for the product during the last 4 complete weeks and divide this by 4 (in case there were 4 complete weeks) to calculate the average. When there were less than 4 complete weeks, the total will be divided by the actual number of complete weeks. '|| chr(10) ||'1 = Calculate the average number of items delivered per delivery'|| chr(10) ||'Determine the total number of items that has been delivered for the product (just as for  option 0) and divide it by the number of deliveries that has been done during these last 4 weeks. '|| chr(10) ||''|| chr(10) ||'Only relevant when the module LVMINTERNET is in the license.', 'N');
execute CreateSystemSetting('Linen Recording', 'WEEKSAVGCALCDELSTD', '13', 'I', '13', 'N', 'N', 2, 99, '', 'Number of weeks over which the average delivery standards quantities are calculated. Module AVERAGEBASEDSTANDARDS should be in the license of the plant. Products in cons point logistic should be set to usage based standards. Scheduled process average calculation standard deliveries is doing the calculatons. ', 'N');
execute CreateSystemSetting('Linen Recording', 'WEIGHTDECIMALSMANUALINPUT', '1', 'I', '1', 'N', 'Y', 1, 2, '', 'Number of decimals for manual input of weigths, i.e. in the Delivernote from.', 'N');
execute CreateSystemSetting('Linen Recording', 'WEIGHTDEVIATIONPERC', '0', 'F', '0', 'N', 'N', 0, 100, '', 'Used in bulk delivery note dialog. Before processing a bin a verification is done on the entered weights. The theoretical weight is calculated based on the theoretical weight of the product and it is compared with the weight of the bin. A deviation up to a certain percentage is allowed. This percentage is stored in this system setting. Fill 0 if no check needs to be performed', 'N');
execute CreateSystemSetting('Stockroom', 'ADVPURCHPRICETERMSPRIO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls how to search for the applicable price terms when generating purchase requisitions and if the default delivery days as defined for the default ordering terms may be overridden automatically. Possible values:'|| chr(10) ||'0 - Search for price terms based on the number of delivery days as defined for the default ordering term'|| chr(10) ||'1 - Search for volume price with lowest delivery term for given quantity and override the default delivery days of the default ordering term'|| chr(10) ||'2 - Search for volume price with lowest price for given quantity and override the default delivery days of the order terms when applicable'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module ADVANCEDPURCHASING is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWALTERNATIVESIZES', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting can be used to configure whether alternative sizes should be used when checking for available stock and/or creating reservations. By default it is set to ''N'', so no alternative sizes will be used in the search for available stock.'|| chr(10) ||''|| chr(10) ||'Only the setting of plant from the stockroom with priority 1 will be taken into accoun. If no items can be found on the priority 1 stockroom and the system starts with a search in the next stockroom accoridng to the priority, it is not needed to check if it concerns another bu/plant.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHANGEISSUESUBST', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = When issueing a substitute product/size, item can only be issued as a substitute.'|| chr(10) ||'1 = When issueing a substitute, item can either be issued as a substitute or can be changed to requested product/size (user choice)', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHANGEPRINTEDWO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to make changes to an existing work order line, or to add a new work order line for a work order that has been printed (WorkOrder.WorkOrderPrinted = Y), unless it has been completely cancelled or completed, or any items have been ordered for it on a purchase order. When the work order has either been cancelled or completed, or items have been ordered for it (WorkOrder.Ordered = Y) then it is never allowed to make any changes, regardless of the fact whether it has been printed or not. Possible values:'|| chr(10) ||'0 = Do not allow to make changes to a work order that  has been printed'|| chr(10) ||'1 = Do allow to make changes to a work order that has been printed', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHANGEPURCHREQCALC', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'This setting controls whether it is allowed to exclude picking locations from the purchase request generation process. When excluded this implies that all items that are stored on these picking locations will be ignored when generating any purchase requests based upon minimum stock quantities. As a result of that more items might be ordered than was actually needed.'|| chr(10) ||'Possible values  '|| chr(10) ||'0 = Do not allow to exclude (default)'|| chr(10) ||'1 = Allow to exclude'|| chr(10) ||''|| chr(10) ||'When set to 0, then the user can cannot uncheck the Include in Purchase Request Calculation checkbox in the Location Type dialog, when the Picking Location checkbox is set to checked. Only when set to 1, the user is allowed to uncheck it while the Picking Location checkbox is checked. ', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHANGEQTYORDERED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting will be used to configure whether it is allowed to make adjustments to the quantities delivered/dismounted when compared to the quantities requested for a mounting/dismounting order. These adjustments will be made in the "Mounting Order" maintenance screen. When it is set to "N", this implies that always will be delivered/dismounted what is requested via the contract lines. By default it will be se to "Y". '|| chr(10) ||'"N" = No adjustments can be made'|| chr(10) ||'"Y" = Adjustments may be made', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHANGETOLAUNDRYSTOCK', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Do not allow transfer from Customer related / Customer owned to general laundry stock.'|| chr(10) ||'1 = Allow with a move stock transfer to change property from Customer related / Customer owned to general laundry stock. When transfer is done, warning pop up is shown.'|| chr(10) ||'2 = Allow with a move stock transfer to change property from Customer related / Customer owned to general laundry stock.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCHIPNOWLATER', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Via this setting it can be controlled if it should be possible to fill both a scanned chip code as a secondary key and a generated barcode as a primary key when issueing non-unique item in the various  "Issue" dialogs (except for "Issue Sales Items" and "Issue Stock Delivery" dialogs).  When enabled, the user has to indicate whether the chip code will be scanned now, or later, but in both cases a barcode will be generated and stored as a primary key.  Only when the option Chip Now was chosen, the user has to scan a chip code and the scanned chip code will be stored for the unique item as a secondary key. Possible values:'|| chr(10) ||'0 - The option chip item now/later will never be visible (default)'|| chr(10) ||'1 - The option chip item now/later will be visible and option Chip Now is selected by default'|| chr(10) ||'2 - The option chip item now/later will be visible and option Chip Later is selected by default', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCOGSALES', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Do not allow to issue a customer-owned item for sales'|| chr(10) ||'1 = Allow to issue a customer owned item for sales, show warning.'|| chr(10) ||'2 = Allow to issue a customer owned item for sales, no warning.'|| chr(10) ||'In case of option 1/2 the item will be issued but not charged (sales history will have status ''free of charge'')', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCOMBINEDPURCHASEPRIO', '2', 'I', '2', 'N', 'N', 0, 2, '', 'This setting is used to define whether the priority of a purchase request should be taken into account when generating purchase orders based on purcases requests. Possible values:'|| chr(10) ||'0 - No combinations allowed. Priority will be set to priority of selected purchase request(s).'|| chr(10) ||'1 - Allow to combine priorities 1 + 2. Priority will be set to 1. '|| chr(10) ||'2 - Allow to combine priorities 1 + 2. Priority will be set to 2. (Default)', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWCOMBPURCHASECATEGORY', '1', 'I', '1', 'Y', 'N', 0, 1, '', 'This setting is used to define whether the purchase category of a purchase requisition should be taken into account when generating purchase orders based on purchase requisitions. Possible values:'|| chr(10) ||'0 - No combinations allowed. Purchase category will be set to purchase category of the selected purchase requisition(s).'|| chr(10) ||'1 - Allow to combine purchase categories. Purchase category will be set to 1 (All categories) '|| chr(10) ||'This setting is only relevant when the module ADVANCEDPURCHASING is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLICATESALESPERSON', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-rmessage will be raised in the "Sales Note" dialog when manually adding a new sales note or changing an existing (not yet invoiced) sales note and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the system settings KEEP1SALESPERSONSALESNOTE and KEEP2SALESPERSONSALESNOTE both have a value > 0, otherwise it is not possible to enter a primary and a secondary sales person at a sales note.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONACTCU', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Customer Activity" dialog when manually adding a new customer activity or changing an existing customer activity and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a customer activity.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONACTPC', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Activities Per Postal Code" dialog when manually adding a new activity for a postal code or changing an existing activity for a postal code and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter an activity for a postal code anyway.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONCPL', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Rental Quantity Adjustment" dialog when manually adding a new adjustment or changing an existing adjustment and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a rental quantity adjustment.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONCUST', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Customer" dialog when manually adding a new customer or changing an existing customer and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a customer.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONMO', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Mounting Order" dialog when manually adding a new mounting order line or changing an existing (not yet invoiced) mounting order line and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a mounting order line.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONPC', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Postal Code Per Country" dialog when manually adding a new postal code or changing an existing postal code and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a postal code.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONPLPC', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Product List Per Customer" dialog when manually adding a new customer product or changing an existing customer product and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a customer product.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWDUPLSALESPERSONSN', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "N" then an error-message will be raised in the "Sales Note" dialog when manually adding a new sales note line or changing an existing (not yet invoiced) sales note line and the primary and secondary sales person are identical.'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the module ZIPSALESEMPLOYEE is in the license of the plant, otherwise it is not possible to enter a primary and a secondary sales person for a sales note  line.', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWEDITPOPRIORITY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to change the priority code for a purchase order as long as it has not been sent to a supplier.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = It is not possible to change the priority code for a purchase order (default behaviour)'|| chr(10) ||'1 = It is allowed to change the priority code for a purchase order as long as it has not been sent to a supplier yet'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the KLHCUSTOM module is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWEDITWOREASONCODE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to change the reason code for a work order as long as it has not been linked to a purchase order via any of its work order lines.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = It is not possible to change the reason code for a work order (default behaviour)'|| chr(10) ||'1 = It is allowed to change the reason code for a work order as long as it has not been linked to a purchase order yet'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the KLHCUSTOM module is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWGRADECHANGEUPONMOVE', 'N', 'B', 'N', 'Y', 'Y', null, null, '', 'This setting will be used to configure whether it is allowed to make a change to the quality grade of the items that are moved from one location to another location within the same stockroom. By default it will be se to "N". '|| chr(10) ||'"N" = No change in grade can be made'|| chr(10) ||'"Y" = Changes to the grade may be made', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWPARTIALAPPROVALSDO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if it will be possible to manually approve individual order lines for a Stock Delivery Order (for internal purchasing) from within the Intercompany Ordering Monitor dialog.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not allow to approve single SDO lines'|| chr(10) ||'1 - Do allow to approve single SDO lines only'|| chr(10) ||'2 - Do allow to approve single SDO lines as well as to approve an SDO as a whole'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the mdoules MAG and ADVANCEDPURCHASING are both in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWPARTIALCANCELSDOLINE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if it will be possible to partially cancel an SDO line from within the Intercompany Ordering Monitor dialog. Cancelling an SDO line as a whole is always allowed from within this dialog and the user is only asked for confirmation if he is sure that the selected SDO lines will be cancelled, regardless of the fact if the user selects one or more SDO line . In case it is allowed to partially cancel an SDO line, then only when the user selects a single SDO line, the user is asked to enter the number of items to be cancelled. Possible values:'|| chr(10) ||'0 = Do not allow to partially cancel an SDO line'|| chr(10) ||'1 = Do allow to partially cancel an SDO line'|| chr(10) ||'This setting is only relevant when ADVANCEDPURCHASING module is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWPARTLYISSUEINTPO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to receive any goods from an internal purchase order, when the corresponding stock delivery order has not been completed yet. By default 0 is selected.'|| chr(10) ||'Possible values:'|| chr(10) ||'0: It is not allowed to receive any items on an internal purchase order, when the corresponding stock delivery order from the supplying stockroom has not been completely issued yet.'|| chr(10) ||'1: It is allowed to receive any items on an internal purchase order, although the corresponding stock delivery order from the supplying stockroom has not been completed yet. Its state should be either "In progress", "In progress with priority" or "Completed".', 'N');
execute CreateSystemSetting('Stockroom', 'ALLOWSUBSTITUTES', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Issue screens: Only when set to Yes the user can issue substitutes.'|| chr(10) ||'This setting is not applicable for issue pool items.', 'N');
execute CreateSystemSetting('Stockroom', 'APPARELEXPORTLAYOUT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Only used for module Apparel Interface.'|| chr(10) ||'0 = One PO for general layout, PO per customer for personalized orders.'|| chr(10) ||'1 = For general PO split lines per wearer and product, PO per customer for personalized orders.', 'N');
execute CreateSystemSetting('Stockroom', 'AREACODELENGTH', '12', 'I', '12', 'Y', 'N', 0, 12, '', 'This setting will be used to define the maximum length for the area code of the stockroom location. When defined as a fixed default, then the field is mandatory. When defined as an overruleable default, the field is optional and may be left empty. A value 0 implies that no area code can be defined in the Stockoom Location dialog.'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when setting USESTOCKROOMLOCATIONAREA = 1.', 'N');
execute CreateSystemSetting('Stockroom', 'ASSIGNCHIPBUFILTER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting can be used to filter items based on processing business unit of item in ASSIGNCHIPSCAN screen.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = only items that belong to current business unit are allowed ( default value). Assign chip is made from local business unit.'|| chr(10) ||'1 = no filter for processing business unit of item to allow assign chip action from business unit that issue the item. Assign chip is made by business unit that manage the stockroom that issue item.', 'N');
execute CreateSystemSetting('Stockroom', 'AUTOFILLLOCATIONUNIQUEID', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is used to configure whether the unique ID to identify a stockroom location is an optional field that will be entered from the user, or a mandatory field that will be filled in automatically based upon the combination of area code, row code and location code. Possible values:'|| chr(10) ||' 0 = Do not fill automatically (default)'|| chr(10) ||' 1 = Fill automatically and read only', 'N');
execute CreateSystemSetting('Stockroom', 'AUTOMPROCINTPO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting defines to what degree the processing of an internal purchase order is automated. Either, all steps should be done, which is similar to the processing of a regular external purchase order. Or some steps are done automatically. Possibly the approval is automated as well. Possible values:'|| chr(10) ||'0 = No automated processing'|| chr(10) ||'1 = Semi-automated processing without approval of internal purchase order'|| chr(10) ||'2 = Semi-automated processing with approval of internal purchase order'|| chr(10) ||'Confirmation of an internal purchase order will not be done automatically after this approval process from the ordering stockroom. The confirmation will only be done automatically at the moment when the generated SDO has actually been approved from the supplying stockroom and this system setting has a value 1 or 2', 'N');
execute CreateSystemSetting('Stockroom', 'AVAILABILITYCALCULATION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = When there are more work orders reserving the same product / size they get status "available with shared reservation". It is upto the user to determine which is issued and which not.'|| chr(10) ||'1 = When there are more work orders reserving the same product / size the first needed will be served first.', 'N');
execute CreateSystemSetting('Stockroom', 'BUFILTERONCUSTOMERS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is used to control whether a filter on business unit should be applied with respect to the selection of customers (and their respective work orders) in the Work Order Status Control and Maintain Sales Notes dialog. Either all customers (and their work orders) may be selected, or only those customers that either have the current business unit as their default business unit or that have at least one activity that is being processed by the current business unit. Possible values:'|| chr(10) ||'0 = Do not filter on business unit'|| chr(10) ||'1 = Do filter on business unit'|| chr(10) ||'Fixed values, default 0', 'N');
execute CreateSystemSetting('Stockroom', 'CALCMETHODWOEDD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Determines the calculation formula of the Expected Delivery Date (EDD) on Work Order Line level. Start date is a variable value. Depending on the case it can be the entry date of the work order, it can be the supplier confirmation date or it can be a date coming from a third party application. Possible values:'|| chr(10) ||'0 -  %STARTDATE% + Service days [workdays1] + Pre-wash days [workdays3] + Logistical scheme days'|| chr(10) ||'      [workdays2] + delivery scheme / route scheme (garments) of the customer / delivery point'|| chr(10) ||'1 -  %STARTDATE% + Service days [workdays1] + Logistical scheme days [workdays2] + Pre-wash days'|| chr(10) ||'      [workdays3] + delivery scheme / route scheme (garments) of the customer / delivery point'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the EXTENDEDCUSTOMERSERVICE module is active', 'N');
execute CreateSystemSetting('Stockroom', 'CALCMETHODWOISD', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Determines the calculation formula of the Internal Shipping Date (ISD) on Work Order level. Start date is a variable value. Depending on the case it can be the entry date of the work order, it can be the supplier confirmation date or it can be a date coming from a third party application. Possible values:'|| chr(10) ||'0 -  %STARTDATE% + Service days [workdays1] + Pre-wash days [workdays3]'|| chr(10) ||'1 -  %STARTDATE% + Service days [workdays1] '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the EXTENDEDCUSTOMERSERVICE module is active', 'N');
execute CreateSystemSetting('Stockroom', 'CANCELREPLWOLUPONDELPREQ', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if only the link between the purchase requisition and a replenishment work order line should be deleted when the purchase requisition is deleted, or if the originating replenishment work order line should be cancelled as well. Possible values:'|| chr(10) ||'0 = Do not cancel the replenishment work order line'|| chr(10) ||'1 = Cancel the replenishment work order line', 'N');
execute CreateSystemSetting('Stockroom', 'CHECKDISMOUNTINGINADVANCE', '1', 'I', '1', 'N', 'N', 1, 9999, '', 'This setting will be used to configure the days in advance that the possible route for a dismounting order should be determined before the expected dismounting date. ', 'N');
execute CreateSystemSetting('Stockroom', 'CHECKMOUNTINGINADVANCE', '5', 'I', '5', 'N', 'N', 1, 9999, '', 'This setting will be used to configure the days in advance that the availability for a mounting order should be checked before the expected mounting date. ', 'N');
execute CreateSystemSetting('Stockroom', 'CHECKSCANITEMSDAYS', '0', 'I', '0', 'N', 'N', 0, 7, '', 'Number of days till which an item is still marked as scanned in Stockroom inventory quick scan. 0 means that only scanned items from current day are inventoried. All items not inventoried or inventoried older then the number of days configured with this setting are moved into INSPECT locations.', 'N');
execute CreateSystemSetting('Stockroom', 'CONFIRMEMBLEMOPTION', '1', 'I', '1', 'Y', 'N', 0, 2, '', '0 = After issue, even when emblems are needed, no emblems will be attached to unique item.'|| chr(10) ||'1 = After issue, a pop-up is shown to confirm the attachment of emblems.'|| chr(10) ||'2 = After issue, when emblem are needed they will always be attached to unique item without confirmation.'|| chr(10) ||'Remind : this setting is only for garments, not for pool items', 'N');
execute CreateSystemSetting('Stockroom', 'CONFIRMEMBLEMS', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Issue Screens: defines if the user needs to confirm that the required emblems a placed, or not.'|| chr(10) ||'If yes a popup screen will be shown after pressing the issue button, in which the user can confirm'|| chr(10) ||'the emblems one by one or all.'|| chr(10) ||'Remind : If you want to charge emblems for first delivery you have to confirm during issue.'|| chr(10) ||''|| chr(10) ||'THIS IS BEING REPALCED BY CONFIRMEMBLEMOPTION FROM 9.05', 'N');
execute CreateSystemSetting('Stockroom', 'CONFIRMPICKNOSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether unique items should be scanned when confirming a unique pick list or not.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Unique items must be scanned individually as confirmation'|| chr(10) ||'1 = The number of picked unique items is confirmed', 'N');
execute CreateSystemSetting('Stockroom', 'DEFAULTRCRECEIVEEXTPO', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'Default reason code used in Receive items from External purchase order. This reason code should be  selectable in Receive items from Purchase order screen.', 'N');
execute CreateSystemSetting('Stockroom', 'DEFAULTREQUESTEDDELDAYS', '1', 'I', '1', 'N', 'N', 0, 14, '', 'Minimum number of days to determine the needed date for generating a work order. This number will be added to the systemdate to get the first possible date. The needed date will be set to the first delivery date of the customer >= first possible date.'|| chr(10) ||'Saturday and sunday are also counted.'|| chr(10) ||'For example, if set to 3 then a work order can not be created for being issued within 3 days, it must be for the first delivery after 3 days.', 'N');
execute CreateSystemSetting('Stockroom', 'DEFAULTSCANORGENERATE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls the option that will be selected by default within the generic Issue WorkOrder dialog in case the items are to be issued unique coded. Possible values:'|| chr(10) ||'0 = select option Scan ID code by default'|| chr(10) ||'1 = select option Generate ID code(s) by default', 'N');
execute CreateSystemSetting('Stockroom', 'DEFAULTSERVICEDAYS', '0', 'I', '0', 'Y', 'Y', 0, 14, '', 'This setting defines the number of days that will be added to the confirmed delivery date as provided from the supplier to calculate the expected fulfillment for those work orders that are depending on the delivery of these items from the supplier and that require any additional activities from the laundry before they can be delivered to the customer.'|| chr(10) ||''|| chr(10) ||'If set to 3 for example then this implies that a work order will normally not be delivered to a customer earlier than 3 days after the final reception of the goods from a supplier since the laundry needs these 3 days to do all necessary actions before they can be delivered. ', 'N');
execute CreateSystemSetting('Stockroom', 'DEFAULTSTARTRENT', '1', 'I', '1', 'Y', 'N', 1, 5, '', 'Issue Screens: Defines the default value for the "Start rent"-field.'|| chr(10) ||'Note that the option that is defined as default here, should be activated by its specific setting.'|| chr(10) ||'1=Today'|| chr(10) ||'2=At Delivery'|| chr(10) ||'3=At Moment of take In Use'|| chr(10) ||'4=At Fixed Future Date'|| chr(10) ||'5=At Fixed Past Date'|| chr(10) ||'Recommended use: 1-Today.', 'N');
execute CreateSystemSetting('Stockroom', 'DEFINEDEFAULTSUPPLIERPLPC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to define a default supplier at PLPC level for a product/size combination. Allowed values:'|| chr(10) ||'0 – No default supplier can be defined for a customer product (current behavior)'|| chr(10) ||'1 – A default supplier may be defined for a customer product', 'N');
execute CreateSystemSetting('Stockroom', 'DEFPREQSUPPLIERPRIORITY', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls which criterion will be used to determine which supplier should be the default supplier for the generated Purchase Request. Possible values:'|| chr(10) ||'0 - Default supplier as defined for stockroom product/size combination'|| chr(10) ||'1 - Supplier having the best price '|| chr(10) ||'2 - Supplier having the best delivery terms', 'N');
execute CreateSystemSetting('Stockroom', 'DEFPRODSELSALESORDER', '1', 'I', '1', 'Y', 'N', 1, 2, '', 'Depending on this setting, the user is allowed to either select all active products when manually creating a  sales order line or only those products that are defined in the PLPC. Possible values:'|| chr(10) ||'1 - Only products from PLPC may be selected'|| chr(10) ||'2 - All active products may be selected'|| chr(10) ||''|| chr(10) ||'When defined as a default value, the user has the possibility to overrule the default as provided by the system when adding a sales order line. When defined as a fixed value, the user cannot overrule this setting.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the TRADE module is in the license.', 'N');
execute CreateSystemSetting('Stockroom', 'DEFSUPPLIERPERPRODUCTSIZE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to define a default supplier per product/size level. By default this is not possible and one can only define it per stockroom/product via the Modify Stock Quantities per Product dialog. The value defined here will be applied to all sizes belonging to this product. Allowed values:'|| chr(10) ||'0 = Enabled (default)'|| chr(10) ||'1 = Not Enabled'|| chr(10) ||''|| chr(10) ||'When enabled, it will no longer be possible to define a default stockroom per product from within the Modify Stock Quantities per product dialog. In that case, it will only be possible via the Default Supplier Product dialog or the Default Supplier per product Size dialog.', 'N');
execute CreateSystemSetting('Stockroom', 'DELSCANCREATIONBUOFWO', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting defines whether the delivery scan for the issued items should be created for the processing BU that actually issues the items for the Work Order (as it is standard), or for the BU that has created the Work Order. This determines for instance where the turnover will be registered.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Delivery scan is registered for the BU that issues the item for a Work Order (Default)'|| chr(10) ||'1 = Delivery scan is registered for the BU that has created the Work Order', 'N');
execute CreateSystemSetting('Stockroom', 'DETACHEMBLEMRAG', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Allow the user to detach emblems before ragging (an) item(s). Detached emblems can be returned to stock and reused.', 'N');
execute CreateSystemSetting('Stockroom', 'DETACHEMBLEMRETURNTOSTOCK', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Allow user to detach emblems when items are returned to stock. Detached emblems can be returned to stock to be reused.', 'N');
execute CreateSystemSetting('Stockroom', 'DETERMINESTARTRENT', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = at the moment of issue'|| chr(10) ||'1 = at the moment of making the work order, can NOT be overruled during issue'|| chr(10) ||'2 = at the moment of making the work order, can be overruled during issue', 'N');
execute CreateSystemSetting('Stockroom', 'DRSALESNOTEDIRECTINVOICE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When creating a driver sales note, this note can be invoiced either via a direct invoice or via regular (periodic) invoicing. This must be determined on the note. Notes that are set to be invoiced directly can only be invoiced directly, and not via regular (periodic) invoicing.'|| chr(10) ||'"Y" - Sales notes, based on driver sales should be invoiced directly'|| chr(10) ||'"N" - Sales notes, based on driver sales should be invoiced via periodic invoicing', 'N');
execute CreateSystemSetting('Stockroom', 'EDITABLERENTENDDATE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Issue Screens: Defines if the field "Rent end date" is editable or not. The system will determine in any case a (default) value based on the number of calculation weeks defined for the residual value scheme, defined in productlist per customer.', 'N');
execute CreateSystemSetting('Stockroom', 'EDITMODIFICATIONS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Used for scanning items out of circulation, return to stock:'|| chr(10) ||'0 = Not possible to change the modifications'|| chr(10) ||'1 = Possible to change the modifications', 'N');
execute CreateSystemSetting('Stockroom', 'EXCEEDMAXFREEINVENTORY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting is used to control whether it is allowed to issue more items free-of-charge then defined in the contract at wearer level. Possible values:'|| chr(10) ||'N = No it is not allowed to issue more'|| chr(10) ||'Y = It is allowed to issue more '|| chr(10) ||''|| chr(10) ||'This setting is only relevant for the Work Order FulFillment screen, not for the regular Issue screens. When set to N and a user tries to issue more free-of-charge items than defined in the contract, then an error message is raised and the items cannot be issued. When set to Y, then no warning is raised and the items are issued as free-of-charge even though it exceeds the number of the contract.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPECTEDDELDATEWOENABLED', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Expected delivery date on work order is calculated and cannot be changed manually.'|| chr(10) ||'1 = Expected delivery date on work order is calculated but can be overwritten manually.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTISSUE', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for Issue from stock transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTMOVESTOCK', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for move stock transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTPRICECHANGE', '9999', 'S', '', 'N', 'N', null, null, '', 'Export code for price changes for exporting stock transactions to Exact', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTPRICEDIF', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for receive from PO price difference transaction.'|| chr(10) ||'If empty, price difference is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTPURCHASEORDER', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for receive from PO transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTRAGFROMSTOCK', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for rag from stock transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTRECEIVE', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for receive in stock without PO transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTRETURNTOSTOCK', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for return to stock transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTSALES', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for issue sales from stock transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPEXACTSTOCKCORRECTION', '9999', 'S', '', 'N', 'N', null, null, '', 'Export stock transactions to Exact: Ledger account number for Stock correction transaction.'|| chr(10) ||'If empty, transactiontype is not exported.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPTOISSUEFROMWO2KARDEX', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it should be possible to create an export file or an external automated  storage system (KARDEX) based upon the oustanding items for a work order. This file can be created prior to generating a garment pick list from within the Work Order Status Control dialog. Possible values:'|| chr(10) ||'0 = Do allow to create an export file (default)'|| chr(10) ||'1 = Do not allow the creation of such an export file'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module KARDEXSHUTTLE is in the license, otherwise this functionality is not available.', 'N');
execute CreateSystemSetting('Stockroom', 'EXPTORECEIVEFROMPO2KARDEX', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it should be possible to create an export file for an external automated  storage system (KARDEX) based upon the confirmed and/or received items for a purchase order. This file can be be created upon confirmation of the purchase order or when receiving the goods into stock from a purchase order. Possible values:'|| chr(10) ||'0 = Do only allow to create an export file upon confirmaton of the PO (default)'|| chr(10) ||'1 = Do only allow to create an export file when receiving the goods in stock from PO'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module KARDEXSHUTTLE is in the license, otherwise this functionality is not available.', 'N');
execute CreateSystemSetting('Stockroom', 'EXTENDEDGENPURCHASEREQ', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This system setting determines the layout that is used for the Generate Purchase Orders screen which is opened from the Purchasing dialog.'|| chr(10) ||'0 = Simple layout (default)'|| chr(10) ||'1 = Extended layout', 'N');
execute CreateSystemSetting('Stockroom', 'EXTENDEDREMARKSALESNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Remark length on sales notes.'|| chr(10) ||'0 = Maximum 80 characters'|| chr(10) ||'1 = Maximum 1000 characters', 'N');
execute CreateSystemSetting('Stockroom', 'FIXEDGRADERESERVATION', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting is used to define if reservations should be created for the requested grade or for the highest possible grade (priority 1), when not enough items are available on stock to fulfill the demand for the requested grade. This setting only applies to goods that have an internal supplier as its preferred supplier. When the preferred supplier is an external supplier, then the setting is ignored and always reservations will be made for the highest possible grade (new), when there are not enough items available to fulfill the demand for the requested grade. Possible values:'|| chr(10) ||'N - Reservations will be made in the processing stockroom as defined on the (work) order for the highest possible grade. '|| chr(10) ||'Y- Reservations will be made in the processing stockroom as defined on the (work) order for the requested grade. '|| chr(10) ||'When system setting USESTOCKROOMPRIORITY is set to Y, then the standard behavior will be applied and the current setting is in fact ignored and considered to be set to N.', 'N');
execute CreateSystemSetting('Stockroom', 'FROMUNIQUESTOCK', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Issue Screens: Default value in Issue Garments from Stock -screens: if by default from unique or form not unique stock is picked.'|| chr(10) ||'Recommended use: If stock is mainly not uniquely coded put N, if stock is mainly uniquely coded put Y.', 'N');
execute CreateSystemSetting('Stockroom', 'GENPURCHASEREQFORGRADES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is possible to generate purchase requests for aa product with a grade other than NEW in case of INTERNAL purchase orders. In the standard situation, only items with grade NEW can be ordered via a purchase request. Possible values:'|| chr(10) ||'0 - Purchase requests will only contain products with grade NEW (= standard)'|| chr(10) ||'1 - Purchase requests may contain products with grade NEW or lower'|| chr(10) ||''|| chr(10) ||'This implies that in case there is a demand for grade USED that lead to a reservation for items with grade USED, still items will be ordered on the PO with grade NEW in the default situation. However, when the setting has a value 1, then the actually demanded products with grade USED would be ordered.', 'N');
execute CreateSystemSetting('Stockroom', 'GRADEOVERUNIQUELYCODED', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls how to reserve any items in case not sufficient items are available on stock. When requesting uniquely coded items, by default the reservation mechanism first checks for any unique items having a higher grade, before checking for any non-unique items (since they usually are only new). This is not always desired; therefore, it is possible now to change the behaviour and to switch the order of the checks. Possible values:'|| chr(10) ||'1 - Use the standard mechanism'|| chr(10) ||'2 - Grade has priority over uniquely coded', 'N');
execute CreateSystemSetting('Stockroom', 'IMPROVEDISSUEFROMWOSC', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'If setting is "Y" a new issue screen will be used from the work order status control screen. This screen requires less user interaction. '|| chr(10) ||'If setting is "N" then the existing issue screens are called.', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKISSUE', '0', 'I', '1', 'N', 'N', 0, 1, '', 'When set to 1, a button for issue work order is available in the issue stock quantities screen (work order reservations screen).', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSELECTIONS', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether the "Inquiry Stock Quantity" form will be enhanced with two selections on plant and business unit. By default only a selection on a stockroom connected to the current business unit is possible. '|| chr(10) ||'N - Only stockrooms connected to current business unit can be selected'|| chr(10) ||'Y - One can select a plant and a business unit for that plant. Based on this one can select only stockrooms connected to the selected business unit.', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWAVAILABLE', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Available" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Available". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Available" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWBLOCKED', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Blocked" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Blocked". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Blocked" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWDEFECT', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Defect" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Defect". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Defect" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWPICKED', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Picked" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Picked". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Picked" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWSERVICE', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Service" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Service". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Service" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWTRANSIT', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Transit Out" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Transit Out". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Transit Out" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWTRANSITIN', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Transit In" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Transit In". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Transit In" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INQUIRYSTOCKSHOWVALUE', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether a read-only field/column "Total Product Value" should be displayed in the "Inquiry Stock Quantity" form or its detail forms "Stock Quantity per Product" and "Stock Quantity per Product Size". By default the field/column will not be shown. '|| chr(10) ||'N - Do not display the field/column "Total Product Value". In case of a column, it can also not be selected through the grid option "Show columns".'|| chr(10) ||'Y - The field/column "Total Product Value" will be shown. In case of a column, it its still possible to hide the column by means of the grid option "Show columns".', 'N');
execute CreateSystemSetting('Stockroom', 'INTERNALPREQGENERATION', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is used when generating purchase requests for internal purchase of slow mover products. It is used to control whether the demand should be covered completely via internal purchase, or if it should be covered by internal purchase as far as possible. In that case the remainder could be ordered via external purchase. Possible values:'|| chr(10) ||'0 = Do allow partial supply via internal purchase (combined with external purchase) '|| chr(10) ||'1 = Do not allow partial supply via internal purchase'|| chr(10) ||''|| chr(10) ||'When defined as fixed, it is mandatory to fill the code, when defined as overuleable default it is optional.', 'N');
execute CreateSystemSetting('Stockroom', 'ISSUENOTAVAILABLEALLOWED', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'This setting can be used to define whether or not it is allowed to issue items from non-unique stock if according to the system there is not enough stock available.'|| chr(10) ||'Fixed value, Yes: accept without notice. Stock is decreased until a minimum of 0.'|| chr(10) ||'Fixed value, No: always give error message. User must either use stock correction or issue as many as is available to be able to continue.'|| chr(10) ||'Default value Yes/No: a warning is given and the user must decide whether to continue.', 'N');
execute CreateSystemSetting('Stockroom', 'ISSUEWOALLOWEDITREMARK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting will be used to control whether it is allowed to edit the work order remark from within the generic Issue Work Order dialog.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not allow to edit the work order remark (default).'|| chr(10) ||'1 - Do allow to edit the work order remark.'|| chr(10) ||''|| chr(10) ||'This setting only affects the generic Issue Work Order dialog, not the other specialized issue dialogs.', 'N');
execute CreateSystemSetting('Stockroom', 'ISSUEWORKORDERPRINT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When completing a work order, it is possible to generate and print a delivery note. With this setting set to 1, it is possible to print both the work order and the delivery note.', 'N');
execute CreateSystemSetting('Stockroom', 'ITEMVALUE', '1', 'I', '1', 'N', 'N', 0, 2, '', 'Used in take items out of circulation and maintain unique item screen:'|| chr(10) ||'0 = The value of the unique item is never visible.'|| chr(10) ||'1 = The value of the unique item is displayed on the screen.'|| chr(10) ||'2 = The value of the unique item is displayed on the screen if the user is a system administrator. For other users it is not visible.', 'N');
execute CreateSystemSetting('Stockroom', 'KEEP1SALESPERSONSALESNOTE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'When set to a value > 0 then the user has the possibility to enter the primary sales person (employee of the laundry) for a Sales Note. This can be used for detailed sales tracking per salesman. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 - The field is not visible and the user cannot enter a value for it.'|| chr(10) ||'1 - The field is visible and the user can enter a value for it, however it is still optional.'|| chr(10) ||'2 - The field is visible and the user is obligated to enter a value for it since it is mandatory.', 'N');
execute CreateSystemSetting('Stockroom', 'KEEP2SALESPERSONSALESNOTE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'When set to a value > 0 then the user has the possibility to enter the secondary sales person (employee of the laundry) for a Sales Note. This can be used for detailed sales tracking per salesman. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 - The field is not visible and the user cannot enter a value for it.'|| chr(10) ||'1 - The field is visible and the user can enter a value for it, however it is still optional.'|| chr(10) ||'2 - The field is visible and the user is obligated to enter a value for it since it is mandatory.', 'N');
execute CreateSystemSetting('Stockroom', 'LIMITEDWOLINEACCESS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to modify a work order line once it is in the purchase process. A work order line is considered being purchased when it is either linked to a purchase request or to a purchase order line. Possible values:'|| chr(10) ||'0 = Standard. No limitations (default)'|| chr(10) ||'1 = Restricted. Once linked to a purchase request or purchase order line no changes are allowed to the work order line. ', 'N');
execute CreateSystemSetting('Stockroom', 'LIMITEDWOLINEMODIFICATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to add or change a modification for a work order line that are setup to be executed by an external party. Possible values:'|| chr(10) ||'0 = Standard. No limitations (default)'|| chr(10) ||'1 = Restricted. Once linked to a purchase request or purchase order line for an external supplier, no modifications are allowed to be added to the work order line that are setup as being executed by an external party. ', 'N');
execute CreateSystemSetting('Stockroom', 'LINKPREQ2POREPLPROGRESS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'The setting is used to control how the Quantity on PO for Replenishment column on the first tab of the Purchase Requisition dialog should be calculated. It defines if only purchase order lines (for replenishment) may be selected for which nothing has been received yet, or if the purchase order lines (for replenishment) may have been received partially already. Possible values:'|| chr(10) ||'0 - Only search for PO lines for which nothing has been received yet'|| chr(10) ||'1 - Also search for PO lines that have already been received partially'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when the ADVANCEDPURCHASING module is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'LOCATIONCODELENGTH', '12', 'I', '12', 'Y', 'N', 1, 12, '', 'This setting will be used to define the maximum length for the location code of the stockroom location. When defined as a fixed default, then the field is mandatory. When defined as an overruleable default, the field is optional and may be left empty. ', 'N');
execute CreateSystemSetting('Stockroom', 'MODIFICATIONPERSCAN', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls how the modifications should be handled for the retuned unique items in the Return To Stock or Rag in Batch dialog. The user should either confirm what to do with the modifications for each single scanned unique item, or the user should confirm it only once for all unique items that were scanned to be returned. Possible values:'|| chr(10) ||'0 - Ask the user per scan what to do with the modification(s)'|| chr(10) ||'1 - Enable a button to clear the modification(s) for all scanned unique items', 'N');
execute CreateSystemSetting('Stockroom', 'MOSALESNOTEDIRECTINVOICE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When creating a sales note for a mounting order that contains sold items, this note can be invoiced either via a direct invoice or via regular (periodic) invoicing. This must be determined on the note. Notes that are set to be invoiced directly can only be invoiced directly, and not via regular (periodic) invoicing.'|| chr(10) ||'"Y" = Sales notes, based on mounting order sales should be invoiced directly'|| chr(10) ||'"N" = Sales notes, based on mounting order sales should be invoiced via periodic invoicing', 'N');
execute CreateSystemSetting('Stockroom', 'MOSTATUSCONTROLSELECTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Extra selections in Mounting Order Status Control screen (apart from standard selection on status).'|| chr(10) ||'0 = No extra selection'|| chr(10) ||'1 = Selection on packing department and stockroom available', 'N');
execute CreateSystemSetting('Stockroom', 'MOUNTINGORDERRESERVATION', '1', 'I', '1', 'N', 'N', 1, 3, '', '1 = Reservation should be done immediately after creation'|| chr(10) ||'2 = Mounting order must be approved first before reservation'|| chr(10) ||'3 = Manual selection between option 1 and 2.', 'N');
execute CreateSystemSetting('Stockroom', 'MSNBUFILTERONCUSTOMERS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether a filter on business unit should be applied with respect to the selection of customers (and their respective work orders) in the Maintain Sales Notes dialog. Either all customers (and their work orders) may be selected, or only those customers that either have the current business unit as their default business unit or that have at least one activity that is being processed by the current business unit. Possible values:'|| chr(10) ||'0 = Do not filter on business unit'|| chr(10) ||'1 = Do filter on business unit'|| chr(10) ||'Default 0', 'N');
execute CreateSystemSetting('Stockroom', 'MSNSHOWWAITAPPROVALSO', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Do not show filter on status "Waiting for Approval" in Maintain Sales Notes (default)'|| chr(10) ||'1 = Show filter on status "Waiting for Approval" in Maintain Sales Notes', 'N');
execute CreateSystemSetting('Stockroom', 'NROFWEARERSEXPORTAPPAREL', '10', 'I', '10', 'N', 'N', 0, 9999, '', 'Only used in module APPARELINTERFACE. This setting determines the number of wearers for a small order or a personalized order.', 'N');
execute CreateSystemSetting('Stockroom', 'OPPORTUNITYIDMAXLENGTH', '12', 'I', '12', 'N', 'N', 12, 30, '', 'Maximum length of the Opportunity ID that can be entered for a personalized garment work order, a work order for pool, a sales note or a mounting order.'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when the module SALESFORCE is in the license and will be used in combination with system setting  OPPORTUNITYIDALLOWED.', 'N');
execute CreateSystemSetting('Stockroom', 'OPPORTUNITYIDNULLALLOWED', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether an opportunity ID has to be specified for a personalized garment work order, a work order for pool, a sales note or a mounting order. Possible values:'|| chr(10) ||'0 - Optional (default)'|| chr(10) ||'1 - Mandatory'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when the module SALESFORCE is in the license and will be used in combination with system setting  OPPORTINUTYIDMAXLENGTH.', 'N');
execute CreateSystemSetting('Stockroom', 'PICKGROUPMAXBATCHVALUE', '0', 'I', '0', 'Y', 'N', 0, 9999, '', 'This setting controls the maximum number of items that may be picked from stock in one pick batch. In case a value of 0 is specified, this indicates there is no limit to the number of items that may be picked in 1 batch (pick list).'|| chr(10) ||''|| chr(10) ||'This setting will be used in combination with PICKGROUPMINBATCHVALUE and is only relevant when the module ADVANCEDPICKING is in the license and active.', 'N');
execute CreateSystemSetting('Stockroom', 'PICKGROUPMINBATCHVALUE', '0', 'I', '0', 'Y', 'N', 0, 9999, '', 'This setting controls the minimum number of items that has to be picked from stock in one pick batch. In case a value of 0 is specified, this indicates there is no limit to the number of items that has at least to be picked in 1 batch (pick list).'|| chr(10) ||''|| chr(10) ||'This setting will be used in combination with PICKGROUPMAXBATCHVALUE and is only relevant when the module ADVANCEDPICKING is in the license and active.', 'N');
execute CreateSystemSetting('Stockroom', 'PICKLISTPERSTOCKROOMAREA', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting will be used to configure whether any unique picklists that will be created for the stockrooms of the plant should be per stockroom or per stockroom area. Possible values:'|| chr(10) ||'0 = Picklist per stockroom (default)'|| chr(10) ||'1 = Picklist per stockroom area'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module ADVANCEDPICKING is in the license and active.', 'N');
execute CreateSystemSetting('Stockroom', 'POAPPROVALREFERENCEDATE', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'This system setting is needed in order to determine which date is considered the reference for purchase order approval.'|| chr(10) ||'Possible values:'|| chr(10) ||'1 = system date of the approval of the purchase order'|| chr(10) ||'2 = requested delivery date of the purchase order'|| chr(10) ||'3 = order date of the purchase order', 'N');
execute CreateSystemSetting('Stockroom', 'POAPPROVALRULE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This system setting determines the level of authorization for the approval of purchase orders. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = the basic validation is done by checking the password on stockroom level.'|| chr(10) ||'1 = the validation is done by checking the authorization rule on employee function in combination with the pincode on employee level.', 'N');
execute CreateSystemSetting('Stockroom', 'POIMMEDIATEISSUEWOSELECT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting defines if the user has the possibility to select multiple work order lines for immediate issue when receiving a PO line, or only one single work order line. Possible values:'|| chr(10) ||'0 - Only one single work order line may be selected'|| chr(10) ||'1 - Multiple work order lines may be selected', 'N');
execute CreateSystemSetting('Stockroom', 'POPRINTLANGUAGE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if purchase orders should be printed in the supplier language or the application user language and under which conditions.'|| chr(10) ||'0 = Always use current language as defined for user (like today)'|| chr(10) ||'1 = Always use supplier language'|| chr(10) ||'2 = Print in user language when used for internal use (when approving a PO), print in supplier language when sending to supplier', 'N');
execute CreateSystemSetting('Stockroom', 'POSTATUSCONTROLLAYOUT', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Layout from Purchase Order status control screen:'|| chr(10) ||'0 = One tab with all purchase orders with status new, send and in progress.'|| chr(10) ||'1 = Tab ''To be ordered'' with all purchase orders with status new, and ''Ordered'' with all purchase orders with status send and in progress. The ''To be ordered'' tab is the first tab.'|| chr(10) ||'2 = Same as 1, except ''Ordered'' tab is first.', 'N');
execute CreateSystemSetting('Stockroom', 'PREQLOCKINGDELAY', '5', 'I', '5', 'N', 'N', 0, 60, '', 'Setting to define the number of seconds the purchase request generation process should wait when another purchase request generation process is running for the same stockroom. If it is still locked after this defined interval, then the process stops. 0 means that is stopped immediately when it notices that it is locked for that particular stockroom. ', 'N');
execute CreateSystemSetting('Stockroom', 'PRINTBARCODEONWORKORDER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to yes, the Work Order Number will also be printed as a barcode on the work order (note: barcode font must be installed)', 'N');
execute CreateSystemSetting('Stockroom', 'PRINTLABELRECEIVEONSTOCK', '0', 'I', '0', 'N', 'N', 0, 2, '', 'When generating new ID codes at receiving items on stock:'|| chr(10) ||'0 = No labels are printed'|| chr(10) ||'1 = Confirm label to be printed'|| chr(10) ||'2 = Always print code label'|| chr(10) ||'The code label to be printed is defined in the label layout, with LabelLayout.LabelReceiveOnStock = ''Y''. ', 'N');
execute CreateSystemSetting('Stockroom', 'PRINTONESTEPPICKLISTANDWO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether directly after printing the pick list also all work orders on this pick list should be printed in the same order as they appear on the pick list. Allowed values:'|| chr(10) ||'0 – after printing the pick list there are no work orders printed (default)'|| chr(10) ||'1 – after printing the pick list the work orders will be printed automatically all using the same report template (workorder.rpt)'|| chr(10) ||'2 - after printing the pick list the work orders will be printed automatically using the applicable report template (workorder.rpt for non-sales notes and salesnote.rpt for sales notes)', 'N');
execute CreateSystemSetting('Stockroom', 'PRINTPICKLISTFROMPDA', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting will be used to configure whether a unique picklist should be printed when the user has finshed picking goods from stock for this pick list via a PDA. It will be used as a default value for each stockroom that belongs to a plant, in that way making it possible to have a different setup per stockroom. Possible values:'|| chr(10) ||'0 = Do not print a picklist (default)'|| chr(10) ||'1 = Do print a picklist'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the modules ADVANCEDPICKING and PICKINGASSISTANT are in the license and active.', 'N');
execute CreateSystemSetting('Stockroom', 'PRINTREPLACEMENTSONWO', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Do not print replacement / substitute products on work order'|| chr(10) ||'1 = Always print replacement and substitute products if applicable.'|| chr(10) ||'2 = Print replacement and substitute products only if they are replaced from checkpointscan.', 'N');
execute CreateSystemSetting('Stockroom', 'PROCESSSALESDN', '0', 'I', '0', 'N', 'N', 0, 2, '', 'By this system setting it can be determined what status sales delivery notes get when generating them for the different customer types that are recognized.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 =Immediate processing of trade sales delivery notes when generating them regardless of the customer type.(Default value)'|| chr(10) ||'1 =Not immediate processing of trade sales delivery notes when generating them for all customer types (both internal and external). The generated delivery notes will be generated with status 20 ''In Progress'' and need to be processed in a second step.'|| chr(10) ||'2 =Not immediate processing of trade sales delivery notes when generating them for internal customers (customer type 1 and 2). The generated delivery notes will be generated with status 20 ''In Progress'' and need to be processed in a second step.'|| chr(10) ||'Note: only valid in combination with trade sales module. Not applicable to normal sales work orders.', 'N');
execute CreateSystemSetting('Stockroom', 'PRODUCTWITHMODELSINSTOCK', '3', 'I', '3', 'N', 'N', 1, 3, '', '1 - yes allowed'|| chr(10) ||'2 - give warning'|| chr(10) ||'3 - not allowed'|| chr(10) ||'When an item is received in stock and its product has models attached then'|| chr(10) ||'- for 1 accept it.'|| chr(10) ||'- for 2 then the following warning is given to the user: ''Product has models defined!''. And accept it.'|| chr(10) ||'- for 3 give the following error message to the user: ''You are not allowed to put products in stock that have models connected!'' And reject product.', 'N');
execute CreateSystemSetting('Stockroom', 'PURCHASEWITHOUTOPENORDERS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if it will be possible to generate purchase requests based only on the difference between the number of items on stock and the number of the reservations that has been made for a particular product/size/grade combination. Any defined minimum stock quantities or any already ordered quantities will be ignored completely in this demand calculation. Possible values:'|| chr(10) ||'0 = Include minimum stock quantities and already ordered quantities in the purchase request generation'|| chr(10) ||'1 = Exclude minimum stock quantities and already ordered quantities from the purchase request generation'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when system setting USEWORKORDERPICKING = N', 'N');
execute CreateSystemSetting('Stockroom', 'RAGREASONSTOCKSMARTBC', '-', 'S', '-', 'N', 'N', null, null, '', 'When a smart barcode is placed into stock and then ragged, a rag reason code is needed.  There is no need for the user to be able to select or change this', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORBPSTOCKRETRN', '-', 'S', '-', 'N', 'N', null, null, '', 'reason code used for stock return transactions created by the "Return" process on the bulk packing assistant', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORCREATESBC', '-', 'S', '-', 'N', 'N', null, null, '', 'Reason code used when creating the unique item records for:'|| chr(10) ||' '|| chr(10) ||'A smart barcode in the route returns dialog when module SMARTBARCODE is in the license'|| chr(10) ||''|| chr(10) ||'And service barcode in packing note generation when module UNIQUEITEMSERVICE is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORDISMOUNTING', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used in generation process for dismounting orders.'|| chr(10) ||''|| chr(10) ||'This is also used in module UNIQUEITEMSERVICE as the reason code for removing a cabinet', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORINTERNALPO', '-', 'S', '-', 'Y', 'Y', 1, 6, '', 'Reason code used in generation process from an internal purchase order into a stock delivery order.'|| chr(10) ||'Also used as default reason code for internal purchase orders in receive items from PO screen ', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORMOSALES', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used in confirmation process of mounting order. In case the mounting order contains sold items, a sales note should be created in the background for these sold items.', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORMOUNTING', '-', 'S', '-', 'N', 'Y', 1, 6, '', 'Reason code used in generation process for mounting orders.', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORPACKINGNOTE', '-', 'S', '-', 'N', 'N', 1, 6, '', 'On process packing notes linked to a truck load list, a stock transaction is made with reason code set on this value.'|| chr(10) ||''|| chr(10) ||'This is only applicable when the module WASHROOM is in the license of the plant.', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORPICKING', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when registering picking from stock as a separate step (enabled via system setting  REGISTERPICKINGFROMSTOCK)', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORQMCIRCADJ', '-', 'S', '-', 'N', 'N', null, null, '', 'reason code used for contract dialog, quantity management groups where circulating inventory can be adjusted in the grid and this needs to create a rental quantity adjustment for the change.', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORTOSTOCK', '-', 'S', '-', 'N', 'N', null, null, '', 'This is the reason code used for returning to stock from the route returns WebX dialog', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEFORWICRAG', '-', 'S', '-', 'N', 'N', null, null, '', 'This reason code is used for module WEARERINVENTORYCONTROL (WIC) when garments are being ragged by contract compliancy or the scheduled process to bring circulating inventory in line with the control circulating inventory'|| chr(10) ||''|| chr(10) ||'NOTE: the rag reason used is the one linked to this reason code so please link a rag reason', 'N');
execute CreateSystemSetting('Stockroom', 'REASONCODEMINMAXSTOCKSPLT', '-', 'S', '-', 'N', 'N', 1, 6, '', 'This setting will be used to configure which reason code should be used when generating a purchase order and determination of the purchase order priority for minimum/maximum stock quantity during the purchase order split process.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module POSPLIT is in the license and active.', 'N');
execute CreateSystemSetting('Stockroom', 'RECALCRESERVATIONSALLOWED', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting configures whether the functionality to recalculate stock reservations is available or not from within the "Work Order Status Control" dialog. Default value 0.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Recalculation of stock reservations is not allowed. Button is not available in the "Work Order Status Control" dialog.'|| chr(10) ||'1 = Recalculation of stock reservations is allowed. Button is available in the "Work Order Status Control" dialog.', 'N');
execute CreateSystemSetting('Stockroom', 'RECALCSTOCKRESERVAFTERRAG', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether stock reservations should be recalculated automatically after doing a stock correction or when ragging items from stock. Possible values:'|| chr(10) ||'0 - Do not reclculate the stock reservations'|| chr(10) ||'1 - Do recalculate the stock reservations'|| chr(10) ||''|| chr(10) ||'This setting is only taken into account when no unique pick lists are used for the stockroom.', 'N');
execute CreateSystemSetting('Stockroom', 'RECEIVEPOBYWO', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether it will be possible to make a selection on a specific work order when receiving items from a PO and issue them immediately upon reception. In that way it would be possible to show only the work order lines for a specific work order instead of all work order lines that are connected to the purchase order line.  As a result of that the number of work order lines to pick from for a user is reduced considerably. This is especially usefull in case of large purchase orders. Possible values: '|| chr(10) ||'0 = Do not enable selection on work order'|| chr(10) ||'1 = Do enable selection on work order'|| chr(10) ||''|| chr(10) ||'Only those work orders will be valid that are connected to the selected purchase order line.', 'N');
execute CreateSystemSetting('Stockroom', 'RECEIVESHIPMENTLIST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines the type of automatic collection files'|| chr(10) ||'Possible values: '|| chr(10) ||'0 - No extra step for receiving the shipment list at the local stockroom'|| chr(10) ||'1 - Extra step for receiving the shipment list at the local stockroom'|| chr(10) ||'Value 1 enables and extra button in Shipment List Status Control dialog on the tab-page Completed. This step will then be mandatory.', 'N');
execute CreateSystemSetting('Stockroom', 'RECEIVESTOCKROOMSELECTION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Standard. Select stockrooms managed by and servicing current BU '|| chr(10) ||'1 = Select only stockrooms managed by current BU', 'N');
execute CreateSystemSetting('Stockroom', 'RECORDPASSIVETRUCKSTOCK', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'This setting will be used to configure whether passive stock will be registered at truck level. If that is the case, one can connect a stockroom location of type "SERVICE" to a truck. '|| chr(10) ||'N = No passive stock is registered per truck'|| chr(10) ||'Y = Passive stock is registered per truck', 'N');
execute CreateSystemSetting('Stockroom', 'REGISTERPICKINGFROMSTOCK', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether items will be registered as picked in a separate step before they will be actually issued from stock. By default picking of items is not registered as a separate step. It must be possible to define this setting as a fixed value or a default value. This setting might be overruled at stockroom level when it is a default value.'|| chr(10) ||'"N" - Reserved items will be taken from stock and directly issued to the customer in one action.'|| chr(10) ||'"Y" - Reserved items will be taken from stock and registered as picked. Later on, the picked items will be issued to the customer in a separate step.', 'N');
execute CreateSystemSetting('Stockroom', 'RESERVEUNFINISHEDSIZE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = When making a reservation for purchasing because there is not enough stock available and the size has an unfinished size, then the reservation is made for the unfinished size. This means that the unfinished size is purchased.'|| chr(10) ||'1 = When making a reservation for purchasing because there is not enough stock available, then the reservation is made for the finished size. However, if there is unfinished size available on stock, then this will be reserved first.', 'N');
execute CreateSystemSetting('Stockroom', 'RETURNTOSTOCKINACTIVEONLY', '1', 'I', '1', 'N', 'N', 1, 2, '1', 'This controls what garments can be scanned in the take items out of circulation (return to stock) dialog'|| chr(10) ||'1 = current situation'|| chr(10) ||'2 = only garments that are either for a finished wearer / wearer inventory or have been scanned as Route Returned to Stock (status = 80)', 'N');
execute CreateSystemSetting('Stockroom', 'ROWCODELENGTH', '12', 'I', '12', 'Y', 'N', 0, 12, '', 'This setting will be used to define the maximum length for the row code of the stockroom location. When defined as a fixed default, then the field is mandatory. When defined as an overruleable default, the field is optional and may be left empty. A value 0 implies that no row code can be defined in the Stockoom Location dialog.', 'N');
execute CreateSystemSetting('Stockroom', 'SALESDNONINVOICEDROUTE', '1', 'I', '1', 'N', 'N', 1, 3, '1', 'This defines if when you create a Sales Delivery Note in the TRADE module, under what criteria a route cannot be used for the delivery note.'|| chr(10) ||''|| chr(10) ||'1 = You can have a delivery date where the route has already had invoiced generated'|| chr(10) ||'2 = You cannot have a delivery date where the route has already had invoiced generated'|| chr(10) ||'3 = You cannot have a delivery date where the route has already had invoiced generated and transferred to PDA', 'N');
execute CreateSystemSetting('Stockroom', 'SALESNOTEALLOWPRICECHANGE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Allow to change the sales price in a sales note / credit note. The default price will be taken from the general price list.', 'N');
execute CreateSystemSetting('Stockroom', 'SALESNOTEDIRECTINVOICE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When creating a sales note or credit note this note can be invoiced via a direct invoice or via regular (periodic) invoicing. This must be determined on the sales / credit note. Notes that are set to be invoiced direct can only be invoiced direct, and not via regular (periodic) invoicing.', 'N');
execute CreateSystemSetting('Stockroom', 'SALESNOTERESERVATION', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Sales note will get status ''New'' and is reserved immediately.'|| chr(10) ||'1 = Sales note will get status ''Waiting for approval'' and needs to be approved. As soon as the sales note has been approved, it will no longer be possible to add or delete any lines, or change the lines (except for the cancelled quantity)'|| chr(10) ||'2 = Sales note will get status ''Waiting for approval'' and needs to be approved. The same restrictions should be applied as for setting 0, only the initial status of the sales note is different.', 'N');
execute CreateSystemSetting('Stockroom', 'SHOWDEFAULTRETURNGRADE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls the default returned grade on return items to stock.Possible values:'|| chr(10) ||'0 = Standard. Show default value for return grade '|| chr(10) ||'1 = Leave empty. Do not show any default value for the return grade. The user is forced to enter a new value', 'N');
execute CreateSystemSetting('Stockroom', 'SHOWPOREMARKUPONRECEIPT', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Via this setting it is controlled whether a remark defined for a purchase order header should be shown in the header part of the screen when receiving the goods for a purchase order. The remark is either not shown at all or directly in the form or indirectly as a popup window.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Do not show remark at all (default)'|| chr(10) ||'1 = Show complete remark via popup'|| chr(10) ||'2 = Show complete remark as text box ', 'N');
execute CreateSystemSetting('Stockroom', 'SHOWWORESERVEDUPONRECEIPT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Via this setting it is controlled whether it should be possible or not to view the reserved items for the work orders that are linked to a purchase order line should  when receiving the goods for a purchase order. When enabled the reserved items will be shown in a popup window, just as when viewing them from within the Inquiry stock quantities dialog.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Do not allow possibility to show reserved items linked to purchase order (default)'|| chr(10) ||'1 = Allow possibility to show reserved items linked to purchase order', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENT1TODAY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Issue Screens: Defines if the user may choose the option "Today" in the "Start rent"-field.'|| chr(10) ||'"Today" means that the item is brought in circulation immedately. '|| chr(10) ||'Recommended use: Always Y.', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENT2ATDELIVERY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Issue Screens: Defines if the user may choose the option "At Delivery" in the "Start rent"-field.'|| chr(10) ||'"At Delivery" means that the item is brought in circulation at the moment of making the delivery note based on outscans. This way the rent only starts when the item is really delivered to the customer.'|| chr(10) ||'Till that moment the item gets status "Assigned".'|| chr(10) ||'Recommended use: Y.', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENT3INUSE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Issue Screens: Defines if the user may choose the option "In Use" in the "Start rent"-field.'|| chr(10) ||'"In Use" means that the item is brought in circulation at the moment the user took the item in'|| chr(10) ||'use. This can be moment of inscan.'|| chr(10) ||'Till that moment the item gets status "Assigned".', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENT4FUTUREDATE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Issue Screens: Defines if the user may choose the option "At Future Date" in the "Start rent"-field.'|| chr(10) ||'"At Future Date" means that the item is brought in circulation at the entered date, by a server process,'|| chr(10) ||'or if scanned in earlier then that date, by the inscan screen.'|| chr(10) ||'Till that moment the item gets status "Assigned".'|| chr(10) ||'Recommended use: N. If set to Y, mind to schedule the "Put assigned items in Circ"-process.', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENT5PASTDATE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Issue Screens: Defines if the user may choose the option "At Past Date" in the "Start rent"-field.'|| chr(10) ||'"At Past Date" means that the item is entered now was already in circulation: the rent start date is in the past. This option is developed when i.e. not uniquely coded items are entered and made unique via this screen. Entering a past date has the advantage of having correct depreciation and end of contract date.', 'N');
execute CreateSystemSetting('Stockroom', 'STARTRENTREPLACEMENT', '1', 'I', '1', 'Y', 'N', 1, 2, '', 'This system setting has effect only if DETERMINESTARTRENT > 0 and only for replacements work orders. '|| chr(10) ||'1 = Date of issue'|| chr(10) ||'2 = Moment of delivery (outscan)', 'N');
execute CreateSystemSetting('Stockroom', 'STOCKMOVERDAYS', '31', 'I', '31', 'N', 'N', 1, 365, '', 'This setting is used to define the number of days in the past for which the completed work orders should be taken into account within the automatic scheduled process that is used to determine whether a given product/size combination is a slow mover or fast mover for a particular stockroom. '|| chr(10) ||''|| chr(10) ||'Will be used in combination system setting STOCKMOVERPERC.', 'N');
execute CreateSystemSetting('Stockroom', 'STOCKMOVERPERC', '50', 'I', '50', 'N', 'N', 0, 100, '', 'This setting defines the minimum percentage that will be used within the automatic scheduled process that is used to determine whether a given product/size combination is a slow mover or fast mover for a particular stockroom.  The defined percentage will be compared to the percentage calculated as the sum of the number of items on work orders with a completion date til n days in the past + all future work orders divided by the total economic stock for a product/size for a stockroom'|| chr(10) ||''|| chr(10) ||'Will be used in combination system setting STOCKMOVERDAYS.', 'N');
execute CreateSystemSetting('Stockroom', 'STOCKROOMDELIVERY', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Issue Screens: defines the default value for the radion buttons Direct Stockroom delivery (Y) / Outscan later (N).'|| chr(10) ||'If outscan later then a manual outscan needs to be done to deliver the item.'|| chr(10) ||'If direct stockroom delivery is selected then besides the issue scan also an automatic outscan is done, so that the delivery note can be made directly afterwards.', 'N');
execute CreateSystemSetting('Stockroom', 'SUPPLDELNOENTRYRECEIVEPO', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether it is possible to enter a supplier delivery note when receiving items on stock for an external purchase order. Possible values:'|| chr(10) ||'0 - The field is not visible at all (default)'|| chr(10) ||'1 - The field is visible, but only enabled in case of an external purchase order. It is optional, so it may be left empty'|| chr(10) ||'2 - The field is visible, but only enabled in case of an external purchase order. It is mandatory, so it must be filled and the user is forced to enter a value.', 'N');
execute CreateSystemSetting('Stockroom', 'UNIQUEITEMRESERVATIONRULE', '0', 'I', '0', 'N', 'N', 0, 3, '', 'This setting controls whether any reservations should be made for unique or non-unique items when unique items are requested to be issued and not sufficient stock can be found to fulfill the demand and it does not concern an unfinished size or a standard length. This affects the items that will have to be purchased'|| chr(10) ||'0 = Reserve uniquely coded items'|| chr(10) ||'1 = Reserve non-unique items'|| chr(10) ||'2 = Depending on supplier product in case of default external supplier. In case of  internal supplier same as 0'|| chr(10) ||'3 = Depending on supplier product in case of default external supplier. In case of internal supplier same as 1', 'N');
execute CreateSystemSetting('Stockroom', 'UPDATEEDDONCONFIRMPO', '0', 'I', '0', 'N', 'N', 0, 3, '', 'New system setting for updating Expected  Delivery Date and Internal Shipping Date when confirming PO. Possible values:'|| chr(10) ||'0 = Update all linked WO''s ( default value)'|| chr(10) ||'1 = No updating of linked WO''s'|| chr(10) ||'2 = Update delivered from stock WO''s only'|| chr(10) ||'3 = Update direct PO WO''s only'|| chr(10) ||'ISD is updated only when module EXTENDEDCUSTOMERSERVICE is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'UPDATEGRADEUPONISSUE', '2', 'I', '2', 'Y', 'N', 1, 4, '', 'When issuing garments via Work Order and the quality grade of the issued item differs from the requested (reserved) grade, than the user can be asked for confirmation whether the item should be issued or not. Whether the user will be asked for confirmation or not, will be controlled via this setting. More in particular the fact whether this setting is configured as a "fixed" or a "default" setting. Possible values:'|| chr(10) ||'1. Issue with current grade'|| chr(10) ||'2. Issue and change current grade into requested grade'|| chr(10) ||'3. Do not issue'|| chr(10) ||'4. Only allow issue with requested grade or higher without changing grade of issued item '|| chr(10) ||'The user is only asked for confirmation when the setting is defined as a "default" value. In that case, the option that will be selected by default will reflect the current value of the system setting. However the user may still select a different option and overrule the default.'|| chr(10) ||'When set as "fixed", then the user is not asked for any confirmation and the action will be performed as is. ', 'N');
execute CreateSystemSetting('Stockroom', 'UPDATEMOUNTINGORDPRINTED', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Update the attribute work order printed in work order, via print MO in MO status control screen. This can be used when the work order for mounting is used instead of the picklist.'|| chr(10) ||'0 = Never update'|| chr(10) ||'1 = Always update, set WO printed to Yes.'|| chr(10) ||'2 = Ask user for confirmation. In case confirmed, set WO printed to Yes.', 'N');
execute CreateSystemSetting('Stockroom', 'UPDATEWORKORDERPRINTED', '0', 'I', '0', 'N', 'N', 0, 3, '', 'Update the attribute work order printed in work order, via print WO in WO status control screen. This can be used when the work order is used instead of the picklist.'|| chr(10) ||'0 = Never update'|| chr(10) ||'1 = Always update, set WO printed to Yes.'|| chr(10) ||'2 = Ask user for confirmation. In case confirmed, set WO printed to Yes.'|| chr(10) ||'3 = Always update even when it is not allowed to make any changes to a printed work order (as controlled with system setting ALLOWCHANGEPRINTEDWO).'|| chr(10) ||''|| chr(10) ||'Please note: option 3 is only supported as of release 9.06.00', 'N');
execute CreateSystemSetting('Stockroom', 'USEDISPATCHADVICE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting will be used to control whether the DISPATCHADVICE table should be used or not when closing a shipment for creating a customs file. Possible values:'|| chr(10) ||'0 = Use dispatch advice when closing shipment '|| chr(10) ||'1 = Do not use dispatch advice when closing shipment', 'N');
execute CreateSystemSetting('Stockroom', 'USEGRADECATEGORYDEFECT', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether the new grade category "Defect" will be used at the current plant. By default, it will be set to "N", so only the original categories "New" and "Used" will be allowed. It must be possible to define this setting as a fixed value or a default value.'|| chr(10) ||'N - For the plant only grade categories "New" and "Used" are allowed'|| chr(10) ||'Y - For the plant, all grade categories "New", "Used" and "Defect" may be used.', 'N');
execute CreateSystemSetting('Stockroom', 'USEMOVESTOCKDIALOGEXT', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is used to configure which "Move Stock" dialog should be called from within the "Stockroom Location" dialog. By default the "old" dialog is called.'|| chr(10) ||''|| chr(10) ||'In this old dialog it is possible to move stock from one stockroom to another, even when they belong to different business units. It is not possible to partially move the contents of a stockroom location to another location.'|| chr(10) ||''|| chr(10) ||'With the new dialog it is not possible to move items from one stockroom to another stockroom. Only movements within the same stockroom are possible. In addition to that, it is possible to partially move the contents of a location. In case of unique items, it is possible to enter the ID codes, either by scanning or manual entry to verify that the correct items are moved.'|| chr(10) ||''|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Use the current simple "Move Stock" dialog (default).'|| chr(10) ||'1 - Use the extended but more restrictive "Move Stock Within Stockroom" dialog.', 'N');
execute CreateSystemSetting('Stockroom', 'USEREPLPURCHREQPRIORITY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to define whether some kind of prioritization should be used when generating purchase requests based on minimum stock quantities. Possible values:'|| chr(10) ||'0 - No priorities used (default)'|| chr(10) ||'1 - Use priorities.'|| chr(10) ||''|| chr(10) ||'Either all reservations are processed as a whole (as it is standard), or priority is given to reservations made for replacement work orders. In that case first the reservations due to replacement work orders are collected. In the same way also the already ordered quantities via dedicated purchase orders (for replacement work orders) are determined. A Replacement work order can be identified via its order lines. The order lines should have a reason code that is marked as a replacement trigger. A dedicated purchase order for replacement work orders can be identified via its priority 1. ', 'N');
execute CreateSystemSetting('Stockroom', 'USESTOCKROOMLOCATIONAREA', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting will be used to configure whether an area code will be used to (hierarchically) group stockroom locations within a stockroom. Possible values:'|| chr(10) ||'0 - no area code will be used (default) '|| chr(10) ||'1 - it is possible to define an area code for a stockroom location', 'N');
execute CreateSystemSetting('Stockroom', 'USESTOCKROOMPRIORITY', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This setting will be used to configure whether the system should automatically create reservations in a stockroom other than the initial stockroom using the defined priority when not enough stock is available in the initial stockroom to fill an (work) order. '|| chr(10) ||'N - Reservations may only be made in the processing stockroom as defined on the (work) order. Other stockrooms are not taken into account.'|| chr(10) ||'Y - The system will try to make reservations, starting with the processing stockroom as defined on the (work) order. If not enough stock is available on the initial stockroom, then it will search for items on the other stockrooms that service the current business unit. If still not enough stock is available, then it will make reservations for new items on the stockroom that is defined as the "Ordering" stockroom.', 'N');
execute CreateSystemSetting('Stockroom', 'USESUPPLIERMODELS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls wether a new object supplier model will be used as an extra level above supplier products.Possibe values:'|| chr(10) ||'0 - No use of supplier models as extra level above supplier products.'|| chr(10) ||'1 - Use of supplier models as extra level above supplier products.'|| chr(10) ||'Default value 0'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when module ADVANCEDPURCHASING is in the license', 'N');
execute CreateSystemSetting('Stockroom', 'USEWORKORDERPICKING', 'N', 'B', 'N', 'N', 'N', null, null, '', 'N = don''t use order picking. Purchase orders are generated based on economic stock below minimum stock level'|| chr(10) ||'Y = Use order picking. Purchase orders are based on not picked from stock per work order. Mind that with this setting NO reservations are made on stock for a work order.', 'N');
execute CreateSystemSetting('Stockroom', 'WEARERINVENTORYSELECTION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting defines whether the user has the possibility to select individual wearer inventory lines to create a work order, or if all wearer inventory lines will be selected automatically to create a work order. Possible values:'|| chr(10) ||'0 = All lines are always selected automatically by the system'|| chr(10) ||'1 = The user can manually select (multiple) individual wearer inventory lines', 'N');
execute CreateSystemSetting('Stockroom', 'WORKORDERACCESSRIGHTS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting will be used to configure whether it is allowed to modify a work order that is not processed by current business unit from Work Order Status control dialog.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Standard. No limitations for work orders that have been approved. So it is still possible to make any changes or even cancel it completely. '|| chr(10) ||'1 = Limited. In case the work order is being processed by stockroom from a different business unit, then it is not allowed to make any changes or even cancel it completely for an employee of the business unit that created the work order.  The detail dialog will be opened in Read-Only mode.'|| chr(10) ||'2 = Restricted. In case the work order is being processed by stockroom from a different business unit, then it is not allowed to make any changes or even cancel it completely for an employee of the business unit that created the work order. Modify and Cancel buttons will be disabled so it will not be possible to open the Work Order detail.', 'N');
execute CreateSystemSetting('Stockroom', 'WORKORDERDISCOUNT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Enable to enter discount in work order approval screen, for sales work orders only.', 'N');
execute CreateSystemSetting('Stockroom', 'WORKORDERPRINTVIAWOSC', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Print the work order via work order status control:'|| chr(10) ||'0 = Normal (not split)'|| chr(10) ||'1 = Print the work order splitted per work order line. So for each line a separate document is printed.'|| chr(10) ||'2 = Ask whether work order is printed splitted or normal.', 'N');
execute CreateSystemSetting('Stockroom', 'WORKORDERREASONCHANGE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, it is allowed to change the reason code as long as the status of the work order is Waiting for approval.', 'N');
execute CreateSystemSetting('Stockroom', 'WOSCBUFILTERONCUSTOMERS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether a filter on business unit should be applied with respect to the selection of customers (and their respective work orders) in the Work Order Status Control dialog. Either all customers (and their work orders) may be selected, or only those customers that either have the current business unit as their default business unit or that have at least one activity that is being processed by the current business unit. Possible values:'|| chr(10) ||'0 = Do not filter on business unit'|| chr(10) ||'1 = Do filter on business unit'|| chr(10) ||'Default 0', 'N');
execute CreateSystemSetting('Stockroom', 'WOSTATUSCONTROLDEFBUTYPE', '1', 'I', '1', 'Y', 'N', 0, 2, '', 'This setting is used to control which work orders to show in the Work Order Status Control filtered on business unit.  Possible values:'|| chr(10) ||'1 = Set to Processed by current BU'|| chr(10) ||'2 = Set to Created by current BU', 'N');
execute CreateSystemSetting('Stockroom', 'WOSTATUSCONTROLSELECTIONS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Extra selections in Work Order status control screen (apart from standard selection on status).'|| chr(10) ||'0 = No extra selection'|| chr(10) ||'1 = Selection on packing department and stockroom available', 'N');
execute CreateSystemSetting('ABS', 'ABSHOMEPAGE', 'www.abs-group.nl', 'S', 'www.abs-group.nl', 'Y', 'N', null, null, '', 'ABS Group web page', 'Y');
execute CreateSystemSetting('ABS', 'CONTAINERRECORDING', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if unique container recording module is active'|| chr(10) ||'FIELD WILL BE MOVED TO LICENCE SETTINGS.', 'N');
execute CreateSystemSetting('ABS', 'CREDITCARDGATEWAY', '0', 'I', '0', 'N', 'N', 0, 3, '', 'This systemsetting is only used in combination with the module CREDITCARDINTERFACE to specify the gateway that is used.'|| chr(10) ||'0 = Orbital (Chase Paymenttech)'|| chr(10) ||'1 = EBizCharge (Century Business Solutions)'|| chr(10) ||'2 = FreedomPay using MuleSoft and IDTech'|| chr(10) ||'3 = Card Connect', 'N');
execute CreateSystemSetting('ABS', 'DIRECTSTOPCHANGE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Standard move route, old route gets an end date and the new route a new start date'|| chr(10) ||'1 = Stop is direct linked to the new route. No history', 'N');
execute CreateSystemSetting('ABS', 'STORENONUNIQUEPERLOCATION', 'Y', 'B', 'Y', 'N', 'N', null, null, 'YN', 'This setting will be used to configure whether (passive) stock quantities for non-unique items will be registered per quality grade level or at location level (as for unique items).  '|| chr(10) ||'N - Non-unique items are not stored at location level.'|| chr(10) ||'Y - Non-unique items will be stored at location level.'|| chr(10) ||''|| chr(10) ||'When changing this setting from N, to Y, then some special script(s) should be run. These scripts move the quantities from table STOCKRESERVATIONPERGRADE to STOCKQUANTITY.'|| chr(10) ||''|| chr(10) ||'It concerns the following scripts/procedures:'|| chr(10) ||'- script "Script order 502142.sql"'|| chr(10) ||'- procedure "ConvertnonUniqueStockItems.prc"'|| chr(10) ||''|| chr(10) ||'When something goes wrong, run the following scripts/procedures'|| chr(10) ||'- script "Script Restore Stock backuped tables.sql " '|| chr(10) ||'- procedure "ConvertnonUniqueStockItems.prc"'|| chr(10) ||''|| chr(10) ||'This is a one-way conversion. Changing from Y to N is not supported. Please be aware of the consequences !!!', 'N');
execute CreateSystemSetting('ABS', 'USETREATMENTCHECK', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Do not use the treatment / check scheme functionality. Instead the old functionality for max washes (automatic flag) and special treatment is used.'|| chr(10) ||'1 = New treatment / check schemes replace the automatic flag for max washes and special treatment.', 'N');
execute CreateSystemSetting('ABS', 'WEBSERVICEURL', '.', 'S', '.', 'N', 'N', null, null, '', 'This setting is needed when calling web services via an Oracle procedure. Must be filled with the URL from where the web service is called.'|| chr(10) ||''|| chr(10) ||'Example: http://127.0.0.1:8080/absgenericwebservice/ABSGenericWebService', 'N');
execute CreateSystemSetting('Billing', 'ABUSEANDLOSSSOILCHARGING', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = By generating delivery notes'|| chr(10) ||'1 = By using the soil count history and connect this to the invoices', 'N');
execute CreateSystemSetting('Billing', 'ACCEPTGIROFORMAT', '0', 'I', '0', 'N', 'N', 0, 5, '', '0 = No acceptgiro used'|| chr(10) ||'1 = Reference on acceptgiro format CH1'|| chr(10) ||'     Pos 1 - 6 internal bankcode, 7 - 18 Customer number, 19 - 26 Invoice number, 27 Checkdigit'|| chr(10) ||'2 = Format CH2'|| chr(10) ||'     Pos 1 - 6 Internal bankcode 7 - 14 Invoice date, 15 - 20 Invoice number, 21 - 26 Customernr 27 Checkdigit'|| chr(10) ||'3 = Format DK (Denmark)'|| chr(10) ||'4 = Format DK2 '|| chr(10) ||'5 = Format CH3', 'N');
execute CreateSystemSetting('Billing', 'ALLOWCHANGEDIRECTINVOICE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether it is allowed to change the Direct Invoice checkbox as long as the sales note /credit note has not been invoiced, even when it is in state Completed. Possible values:'|| chr(10) ||'0 = Do not allow change when work order is complete'|| chr(10) ||'1 = Do allow to change when work order is complete'|| chr(10) ||'This system setting works in combination with the other system settings SALESNOTEDIRECTINVOICE, DRSALESNOTEDIRECTINVOICE and MOSALESNOTEDIRECTINVOICE.'|| chr(10) ||''|| chr(10) ||'If any of these 3 system settings is applicable for a work order and it is defined as a fixed default, then it will never be allowed to change the Direct Invoice checkbox for this particular work order, regardless of the value of the current system setting.', 'N');
execute CreateSystemSetting('Billing', 'ALLOWCHARGEDELIVERYFEE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether it should be possible to define a special charge with frequency ''normal visit'' or ''special visit''  for charging a delivery fee when visiting a customer.'|| chr(10) ||'0 - Do not allow use of these special charge (standard)'|| chr(10) ||'1 - Do allow the use of these special charges', 'N');
execute CreateSystemSetting('Billing', 'ALLOWCUSTSPECIFICPRICE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Allow to choose customer specific prices in pricelist per customer', 'N');
execute CreateSystemSetting('Billing', 'ALLOWDEFMISCTURNOVERGRP', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to define a default tax group and turnover group for invoice line type 15 (Miscellaneous). When enabled, they must be filled. Possible values:'|| chr(10) ||'0 - Do not allow definition of a tax group and turnover group (default) '|| chr(10) ||'1 - Do allow the definition of a tax group and turnover group'|| chr(10) ||''|| chr(10) ||'This setting is related to system settings USETURNOVERGROUP and TAXDEFINITION.', 'N');
execute CreateSystemSetting('Billing', 'ALLOWMANUALINVOICEDATE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'If set to Y, the invoice date of manual invoices is entered and remains fixed.'|| chr(10) ||'If set to N, the invoice date is set to the systemdate when a manual invoice is created. When it is finalized, it is overwritten with the date of finalisation.'|| chr(10) ||'This setting is only used in periodical (EU) invoicing, not in direct (US) invoicing.', 'N');
execute CreateSystemSetting('Billing', 'ARAGINGMETHOD', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'This system setting determines the way the aging control displays the data:'|| chr(10) ||'1 = by days (overdue 30 days, 60 days etc.)'|| chr(10) ||'2 = by months (overdue 2 months, 3 months etc.)'|| chr(10) ||'3 = by payment terms (supports both Net x and Running Month+ )', 'N');
execute CreateSystemSetting('Billing', 'ARTRANSFORZEROINVOICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'With this system setting is controlled if the zero-amount invoices should end up (Yes) or not (No) in Account Receivables. '|| chr(10) ||'Yes = Zero Amount Invoice --> AR transactions'|| chr(10) ||'No = Zero Amount Invoice NOT --> AR transactions ', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTDIRECTINVOICE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Yes = Direct invoices are printed to an Ascii-file (always customized)'|| chr(10) ||'No = Direct invoices are printed as (I-net) Crystal Report (standard)', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTORDERFORM', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Yes = OrderForm report will be printed to an customised Ascii-file (ONLY from RouteStautsControl dialogue)'|| chr(10) ||'No = OrderForm report is printed as (I-net) Crystal Report (standard)'|| chr(10) ||''|| chr(10) ||'For NAF:'|| chr(10) ||'Yes = OrderForm report will be printed to an customised Ascii-file (ONLY from RouteStautsControl dialogue)'|| chr(10) ||'No = OrderForm report will be printed to an customised XML-file (ONLY from RouteStautsControl dialogue)', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTROUTESETTLEMNT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Yes = Route Settlement Sheets are printed to an Ascii-file (always customized)'|| chr(10) ||'No =  Route Settlement Sheets are printed as (I-net) Crystal Report (standard)', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTSETTLEDROUTE', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Yes = Settled Route Sheets (=route settlement sheet after complete settlement) are printed to an Ascii-file (always customized)'|| chr(10) ||'No = Settled Route Sheets (=route settlement sheet after complete settlement) are printed as (I-net) Crystal Report (standard)', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTSOILTICKET', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Yes = SoilTickets are printed to an Ascii-file (always customized). '|| chr(10) ||'No = Soil Tickets are printed as (I-net) Crystal Report (standard)', 'N');
execute CreateSystemSetting('Billing', 'ASCIIPRINTSTATEMENT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Yes = Statements are printed to an Ascii-file (always customized). '|| chr(10) ||'No = Statements are printed as (I-net) Crystal Report (standard)', 'N');
execute CreateSystemSetting('Billing', 'AUTOCREATERENTSTOP', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether any temporary delivery stops should be created automatically for all customer CPL lines when defining a non-business day for a customer. In addition to that when deleting any non-business days, the corresponding temporary delivert stops should be removed as well, Possible values:'|| chr(10) ||'0 = Do not create/delete temporary delivery stops automatically when creating/deleting a customer non-business day (default)'|| chr(10) ||'1 = Do create/delete temporary delivery stops automatically when creating/deleting a customer non-business day'|| chr(10) ||'2 = Do create/delete temporary delivery stops automatically when creating/deleting a customer non-business day or a department non-business day'|| chr(10) ||'Option 2 is only supported as of version 9.02.03.a', 'N');
execute CreateSystemSetting('Billing', 'BILLMINAMNTBASEDONDELSCHM', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set minimum is billed for a product when the product is delivered according to delivery schemes, even though no delivered qty can be determined or if delivered qty = 0. ', 'Y');
execute CreateSystemSetting('Billing', 'BM2TEMPORARYSTOPRENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting makes it possible to control whether regular rent, rent for systematic replacement and imagecare should be charged or not when a temporary delivery stop is active for at least one consumption point during the invoice period. Possible vaules:'|| chr(10) ||'0 - Always charge rent (default)'|| chr(10) ||'1 - Do not charge rent when at least one temporary delivery stop is also marked as a rent stop'|| chr(10) ||''|| chr(10) ||'Only when set to 1, it is possible to indicate that no rent may be charged as well at CPL- level'|| chr(10) ||'This setting is only applicable for US direct invoicing. ', 'N');
execute CreateSystemSetting('Billing', 'BM3MAXINVREDUCEDEPOSIT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the Max Inventory should be reduced with the items that are in deposit stock when running the Status Quo Pieces in Circulation process. Possible values:'|| chr(10) ||'0: When calculating the Max Inventory, do not take into account the items on deposit stock (Default).'|| chr(10) ||'1: When calculating the Max Inventory, do take into account the items on deposit stock. The Max. Inventory should be calculated as the Max. inventory of the wearer(s) minus the qty that is on deposit stock. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module DEPOSITSTOCK is active.', 'N');
execute CreateSystemSetting('Billing', 'BM3RENTBASEDONRQA', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls how is calculated the quantity for BM3 circulating inventory when invoicing in advance and module INVOICEPERACTIVITY is not in the license. Possible values:'|| chr(10) ||'0: When calculating the quantity, it should not be taken from RQA (Default).'|| chr(10) ||'1: When calculating the quantity, it should be taken from RQA', 'N');
execute CreateSystemSetting('Billing', 'BM4BILLONBDAYONLY', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'this is to control if billing method 4 charges on a D day or washes are summed up and charged on the next B day'|| chr(10) ||''|| chr(10) ||'0 = Current behaviour of charge regardless of D or B day type'|| chr(10) ||''|| chr(10) ||'1 = The billing will only occur on the "B" day.  The delivery for the "D" day will still be shown on the invoice but not charged.  It will be summed up for the next B day.', 'N');
execute CreateSystemSetting('Billing', 'CANCELLATIONPERCENTAGE', '66', 'I', '66', 'Y', 'N', 0, 100, '', 'This setting will be used to define the percentage that should be taken into account when calculating a cancellation fee for a customer. ', 'N');
execute CreateSystemSetting('Billing', 'CANCELREDELIVERYINVOICE', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0 = Redelivery invoices are cancelled'|| chr(10) ||'1 = Redelivery invoices are disconnected'|| chr(10) ||'2 = Redelivery invoices are not cancelled and remain linked to the stop. They must be handled manually.'|| chr(10) ||'This setting is only used in settlement. Redelivery invoices are invoices that were moved from another day for example because the original stop was marked undeliverable.', 'N');
execute CreateSystemSetting('Billing', 'CASHAPPLEARLYPAYDISCOUNT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0=no default presentation of the calculated payment term related discount'|| chr(10) ||'1=default presentation of the calculated payment term related discount by statement date', 'N');
execute CreateSystemSetting('Billing', 'CASHAPPLICATIONUSED', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Cash application is used'|| chr(10) ||'1 = Cash application is not used'|| chr(10) ||'Based on this setting checks on open AR Transactions are skipped.', 'N');
execute CreateSystemSetting('Billing', 'CASHDELAYCHARGE', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'controls the default value for Cash Delay Charge on the contract and customer dialog'|| chr(10) ||'0 = Cash Delay charge defaults to No'|| chr(10) ||'1 = If the customer or contract is cash on delivery then Cash Delay Charge defaults to Yes', 'N');
execute CreateSystemSetting('Billing', 'CASHDELAYCHARGEPRICE', '0', 'F', '0', 'Y', 'Y', 0, 999, '', 'This is the default value for the cash delay charge price', 'N');
execute CreateSystemSetting('Billing', 'CHAINPERGENERALPRICELIST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Update price list functionality.'|| chr(10) ||'0 = Old behavior, to work without general price list definitions assigned to a chain. (Standard value)'|| chr(10) ||'1 = New behavior to work with general price list definitions assigned to a chain', 'N');
execute CreateSystemSetting('Billing', 'CHANGESPERWEEKPRICING', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 - Find an exact match, or find the nearest number of changes lower the exact match'|| chr(10) ||'1 - Find an exact match, or look for a general price defined by * number of changes', 'N');
execute CreateSystemSetting('Billing', 'CHARGELOCKERSINUSE', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0=Lockers are charged when connected to an active wearer(employment)     (default )'|| chr(10) ||'1=Lockers are charged when connected to an active wearer(employment) and this employment has at least 1 item in circulation.', 'N');
execute CreateSystemSetting('Billing', 'CHARGELOSSFORDECREASEMAX', '0', 'I', '0', 'N', 'N', 0, 1, '', 'If a item is flagged with the automatic flag for decrease of max inventory and it is not returned, AND systemsetting CHARGELOSSFORDECREASEMAX=1 it will be charged for loss.', 'N');
execute CreateSystemSetting('Billing', 'CHARGELOSSUSINGSTAY', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = All uniquely coded garments that are in circulation are charged for loss.'|| chr(10) ||'1 = Only uniquely coded garments that have a stay at the customer (staycode 20 - 29) are charged for loss', 'N');
execute CreateSystemSetting('Billing', 'CHARGERENTWHENNONEINCIRC', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This controls if wearer inventories with all garments at status assigned (so not yet in circulation) that are linked to a PLPC of Billing Method 2 or 3 should charge rent yet.  This applies to US Direct invoicing and Products per wearer billing only.'|| chr(10) ||''|| chr(10) ||'0 = Billing starts when at least one garment is in circulation '|| chr(10) ||''|| chr(10) ||'1 = Billing starts when all garments are status assigned (not necessarily in circulation yet)'|| chr(10) ||''|| chr(10) ||''|| chr(10) ||'NOTE: Billing method 1 is not controlled by this setting and automatically behaves as per this setting being on 1.', 'N');
execute CreateSystemSetting('Billing', 'CHARGEREPLACEMENT', '1', 'I', '1', 'Y', 'N', 1, 2, '', '1: Compare soil count plus replacement with minimum.   '|| chr(10) ||'   For this option the systematical replacements has to be added before compared with minimum. '|| chr(10) ||'   If the outcome of this is below minimum: Charge minimum'|| chr(10) ||'   If the outcome of this is above minimum: Charge minimum + replacement'|| chr(10) ||'2: Compare soil count without replacement with minimum.  '|| chr(10) ||'    For this option the systematical replacements are always charged extra above the minimum. Automatic     replacement to be added after comparing with the minimum.', 'N');
execute CreateSystemSetting('Billing', 'CHARGEREPLACEMENTBASEDRV', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Replacement charge is charged disregarding setting on customer level'|| chr(10) ||'1 = Replacement charge is charged only if customer is set to charge residual value.'|| chr(10) ||'This setting is only applicable for US direct invoicing'|| chr(10) ||''|| chr(10) ||'As of release 9.04.03 this setting is no longer used and only the customer settings are taken into account since there are separate settings for garments and non-garments now.', 'N');
execute CreateSystemSetting('Billing', 'CHARGERVFORRAGFROMSTOCK', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This setting control the ability to charge a residual value if you rag a unique item from stock with a reason code for charge RV'|| chr(10) ||''|| chr(10) ||'0 = default = do not charge'|| chr(10) ||'1 = if the reason code for ragging is set as charge RV = Y then create a charge (so an out of circulation history record is created to make the charge)', 'N');
execute CreateSystemSetting('Billing', 'CHARGESOILWGHTONDELDATE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Charge Soil weights On Delivery date:'|| chr(10) ||'No = The Soilweights should be charged in the period that they are recorded'|| chr(10) ||'Yes =  The soilweights should be charged in the period that the merchandize is delivered back to the customer.', 'N');
execute CreateSystemSetting('Billing', 'CHECKINVOICEBUSINESSUNIT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'For a multi plant organizations where invoicing is done centrally, customers can be processed by one business unit and invoiced by another one. '|| chr(10) ||'For administrative reasons the invoicing business unit can be changed during the invoicing period (i.e. because of a change of bill-to customer). '|| chr(10) ||'If this setting is set to No then the invoice generation process will not check for what invoice business unit the services where recorded, it will invoice them all for the invoice bussiness unit that is defined at that moment in activities per customer.', 'N');
execute CreateSystemSetting('Billing', 'CHILDINVOICESNUMBER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines how are ordered child invoices for the same debtor on finalize consolidated invoices . Possible values:'|| chr(10) ||'0 -  Child invoices are ordered by customer number ascending'|| chr(10) ||'1 -  Child invoices are ordered descending by the absolute value of amount and then by customer number ascending. So child invoices with amount 0 will have the higher suffix', 'N');
execute CreateSystemSetting('Billing', 'CLEANUPWEEKS', '104', 'I', '104', 'N', 'N', 0, 999, '', 'All invoices older then the number of weeks given, will be cleanded up. Cleaning up old invoices will also erase all packingnotes, garment charges etc. linked to the invoices. ', 'N');
execute CreateSystemSetting('Billing', 'CLOSEACTIVITIESFORPERIOD', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is only relevant when the module INVOICEPERACTIVITY is active and it affects only those customers that are setup for splitting invoices per activity and that are being invoiced in-arrear.It set the activities that have not been invoiced for the current invoice period (because there was nothing to invoice) should still be closed (automatically) when generating a TEST invoice. Possible values:'|| chr(10) ||'0.	 = The invoice period should not be closed automatically  '|| chr(10) ||'1.	 = The invoice period should be closed automatically by default', 'N');
execute CreateSystemSetting('Billing', 'CLUSTERSELECTION', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Cluster is selected from bill to customer'|| chr(10) ||'1 = Cluster is selected from del to customer', 'N');
execute CreateSystemSetting('Billing', 'COEFFICIENTCALCULATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is only applicable for invoice frequencies 112, 115, 121, 131, 141 etc, so invoice frequencies with a monthly price.'|| chr(10) ||'0 = The coefficient is multiplied with the price and this newly calculated price is stored on the invoice line. So billed quantity * price = amount.'|| chr(10) ||'1 = The monthly price is stored on the invoice as it is taken from the PLPC or price list. The coefficient is then calculated with the amount.', 'N');
execute CreateSystemSetting('Billing', 'CONSINVRESTRICTDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the user is allowed to change the only include test invoices from date  in the finalize consolidated invoice screen.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Checkbox and date picker are both editable by the user'|| chr(10) ||'1 = Checkbox and date picker are both not editable by the user', 'N');
execute CreateSystemSetting('Billing', 'CONTAINERRENTSTARTRULE', '1', 'I', '1', 'N', 'N', 1, 2, '1', 'this defines when the rent period for a unique container delivered to a customer starts.'|| chr(10) ||''|| chr(10) ||'1 = The container is billed for weekly rent starting 7 days after it was delivered to the customer until the container is returned'|| chr(10) ||'2 = The container is billed for weekly rent from the first day it is delivered to the customer until the container is returned'|| chr(10) ||''|| chr(10) ||'only used for module CONTAINERBILLING', 'N');
execute CreateSystemSetting('Billing', 'CPI_INCREASEPERCENTAGE', '1', 'F', '1', 'N', 'N', 0, 100, '', 'CPI increase percentage:'|| chr(10) ||'Prices will be updated with this Customer Price Index (CPI) percentage if indicated in the contract screen of each customer, that prices will be increased according to this CPI value, instead of with a fixed percentage.', 'N');
execute CreateSystemSetting('Billing', 'CREATEINVOICEPDFEMAIL', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = PDF will be created according setting CREATEPDFINVOICE'|| chr(10) ||'1 = PDF will not be created when invoice is send by email (despite setting CREATEPDFINVOICE). This will be done during the emailing process.', 'N');
execute CreateSystemSetting('Billing', 'CREATEPDFINVOICE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'When printing invoice:'|| chr(10) ||'0 = PDF is only created when invoice is send by fax or email.'|| chr(10) ||'1 = Always create PDF'|| chr(10) ||'2 = PDF is only created when invoice is send by fax or email or EDI.'|| chr(10) ||''|| chr(10) ||'NOTE: this also applies to US Direct invoices so when set on 1, the emailing scheduled process will also create the PDF for non emailed invoices', 'N');
execute CreateSystemSetting('Billing', 'CREATEPDFSTATEMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When sending statements and creating pdf''s'|| chr(10) ||''|| chr(10) ||'0 = only create for statements that are going to be emailed'|| chr(10) ||'1 = create for statements that are going to be emailed AND create pdf''s in the same folder for statements that are not emailed'|| chr(10) ||''|| chr(10) ||'NOTE, option 2 only create the "statement" pdf not any invoices that are could be including in the statement', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDAMEXSTOREID', '-', 'S', '', 'N', 'N', 0, 32, '', 'For non Canadian customers'|| chr(10) ||'Credit card processing store ID used specifically for Freedom pay and American Express Cards.', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDAMEXSTOREIDCA', '-', 'S', '', 'N', 'N', 1, 32, '', 'For Canadian Customers'|| chr(10) ||'Credit card processing store id used specifically for freedom pay and American Express', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDAMEXTERMINALID', '-', 'S', '', 'N', 'N', 0, 32, '', 'Credit card processing TERMINAL ID used specifically for American Express Cards.'|| chr(10) ||'NOTE: if not set, then AMEX cards will use the CREDITCARDTERMINALID value instead', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDAMXTERMINALIDCA', '-', 'S', '', 'N', 'N', 1, 32, '', 'For Canadian customers'|| chr(10) ||'Credit card processing TERMINAL ID used specifically for American Express Cards.'|| chr(10) ||'NOTE: if not set, then AMEX cards will use the CREDITCARDTERMINALID value instead', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDHOST', 'https://', 'S', 'https://testefsnet.concordebiz.com/efsnet2.wsdl', 'N', 'N', 1, 64, '', 'Used in Creditcard module only: '|| chr(10) ||'required for connection with EFS-net.'|| chr(10) ||'For testing: https://testefsnet.concordebiz.com/efsnet2.wsdl'|| chr(10) ||'For live: https://efsnet.concordebiz.com/efsnet2.wsdl'|| chr(10) ||''|| chr(10) ||'also used for FreedomPay and Card Connect', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDSCHEDULEDEFAULT', '1', 'I', '5', 'Y', 'N', 1, 6, '1', 'This is the default credit card payment schedule type in the contract and customer dialogs'|| chr(10) ||'Only used for module CREDITCARDCHARGESCHEDULE '|| chr(10) ||'1 = day x of every month'|| chr(10) ||'2 = Last day of the month'|| chr(10) ||'3 = the xth day of every month'|| chr(10) ||'4 = every x day'|| chr(10) ||'5 = day after billing day'|| chr(10) ||'6 = Fixed schedule', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDSTOREID', '-', 'S', '-', 'N', 'N', 1, 32, '', 'Store ID used with the Creditcard module:', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDSTOREIDCA', '-', 'S', '', 'N', 'N', 1, 32, '', 'For Canadian customers'|| chr(10) ||'Store ID used with the Credit Card module', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDSTOREKEY', '-', 'S', '-', 'N', 'N', 1, 32, '', 'Used only for Creditcard module for Storekey for EFS-net.', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDTERMINALID', '-', 'S', '-', 'N', 'N', 1, 32, '', 'The terminal ID used for the Freedom pay credit card interface.  Only used for module creditcardinterface', 'N');
execute CreateSystemSetting('Billing', 'CREDITCARDTERMINALIDCA', '-', 'S', '', 'N', 'N', 1, 32, '', 'For Canadian customers'|| chr(10) ||'The terminal ID used for the Freedom pay credit card interface'|| chr(10) ||'Only used with module CreditCardInterface', 'N');
execute CreateSystemSetting('Billing', 'CREDITINVOICENUMBER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if the invoice number range for a credit invoice should be the same as for a regular invoice, or if a specific invoice number range will be used for credit invoices. Possible values:'|| chr(10) ||'0 - Do not use a different invoice number range for credit invoices'|| chr(10) ||'1 - Use a dedicated invoice number range for credit invoices', 'N');
execute CreateSystemSetting('Billing', 'CREDITINVOICESERIESLENGTH', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls if an invoice series should be used for credit invoices. Possible values:'|| chr(10) ||'0 - Do not use an invoice series for credit invoices'|| chr(10) ||'1 - Do use an invoice series for credit invoices with a length of 1 character'|| chr(10) ||'2 - Do use an invoice series for credit invoices with a length of 2 characters'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when system setting CREDITINVOICENUMBER = 1, otherwise it will be ignored.', 'N');
execute CreateSystemSetting('Billing', 'CREDITLOSSFORPOOL100%', '84', 'I', '84', 'N', 'N', 0, 999, '', 'This setting is used for the module LOSSFORPOOL only. This setting sets the period in which pool items that are charged for loss are credited for 100 %. The value is the number of days.', 'N');
execute CreateSystemSetting('Billing', 'CREDITLOSSFORPOOL50%', '365', 'I', '365', 'N', 'N', 0, 999, '', 'This setting is used for the module LOSSFORPOOL only. This setting sets the period in which pool items that are charged for loss are credited for 50 %. The value is the number of days.', 'N');
execute CreateSystemSetting('Billing', 'CSVEXPFILENAMEPREFIX', 'Invoice', 'S', 'Invoice', 'N', 'Y', null, null, '', 'Only used for module EXPORTTOCSV. This is the language dependent prefix that should be used when creating a CSV-file as a result of printing an invoice appendix.', 'N');
execute CreateSystemSetting('Billing', 'CURRENCYOBLIGATED', '0', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls whether it is obligated to fill in a currency when making the selections for the Price update per chain dialog. In this way the number of price lists to be processed can be limited. Possible values:'|| chr(10) ||'0 = Currency is optional'|| chr(10) ||'1 = Currency is obligated', 'N');
execute CreateSystemSetting('Billing', 'DAYSINADVANCEANNIVUPD', '3', 'I', '3', 'N', 'N', 0, 365, '', 'Days In Advance to run price update at anniversary date. This price update program is started from the scheduler.', 'N');
execute CreateSystemSetting('Billing', 'DEFAULTMBYOPPERCENTAGE', '0', 'I', '75', 'Y', 'N', 0, 100, '', 'Default percentage for the reduction in Merchandise Buyout charge that Merchandise Buyout protection insurance gives.  Usually 75%', 'N');
execute CreateSystemSetting('Billing', 'DIRECTINVHANDLINGCHARGES', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Garment charges are added on the first invoice.'|| chr(10) ||'1 = Garment charges are only added on the invoice for the billing day of the customer.'|| chr(10) ||'2 = Garment charges are only added on the invoice for the billing day of the product'|| chr(10) ||'This setting is only applicable for US direct invoicing and in combination with DELIVERYDAYS_US = ''Y''', 'N');
execute CreateSystemSetting('Billing', 'EDITPAIDAMOUNT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Allow to edit paid amount in maintain invoices screen. This paid amount has no link with the cash application.', 'N');
execute CreateSystemSetting('Billing', 'ELECTRONICPAYINVSTATUS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines what invoices are taken for payment when the electronic (was called credit card) scheduled payment process is run'|| chr(10) ||''|| chr(10) ||'0 = All settled invoices with invoice date prior to the process run date'|| chr(10) ||'1 = All settled invoices with invoice date prior to the process run date that have been on a statement', 'N');
execute CreateSystemSetting('Billing', 'ENDOFTHEMONTH', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When this setting is on Yes the button end of the month for invoicing is used and users with aceess can determine if the month is closed for invoicing. The date that is entered will be stored as end of the Month and users cannot invoice periods before this stored date.', 'N');
execute CreateSystemSetting('Billing', 'EXCHANGERATEDETERMINATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls how the applicable exchange rate will be determined within the application. It will either be defined as a single value for each currency (compared to the base currency of the plant) or exchange rates will be defined for each desired combination of currencies with a start date, which makes it possible to record an exchange rate history.'|| chr(10) ||'Possible value:'|| chr(10) ||'0 = Single value set on currency level'|| chr(10) ||'1 = Multiple values set on exchange rate level.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the INVOICECURRENCY module is in the license', 'N');
execute CreateSystemSetting('Billing', 'EXCHANGERATESOURCE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the currency exchange rates data is intended to be maintained manually or via an interface to a 3rd party application. Possible values:'|| chr(10) ||'0 = Internal source (manual entry)'|| chr(10) ||'1 = External source (via interface)'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the INVOICECURRENCY module is in the license', 'N');
execute CreateSystemSetting('Billing', 'EXCHRATEDATEDETERMINATION', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'This setting controls from which date the exchange rate is taken when generating an invoice.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Exchange rate is equal to invoice date'|| chr(10) ||'1 = Exchange rate is invoice date - 1 business day *'|| chr(10) ||''|| chr(10) ||'* Business days are Monday to Friday'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the INVOICECURRENCY module is in the license', 'N');
execute CreateSystemSetting('Billing', 'FILLCLUSTER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes then always the Cluster_ID is stored in the invoice header. If set to No then the Cluster_ID is only stored when the invoice is generated via cluster selection.'|| chr(10) ||''|| chr(10) ||'As of release 9.07.01, when set to Yes then the Cluster_ID is also stored in the invoice header in case of a consolidated invoice, or when generating revenue invoices.', 'N');
execute CreateSystemSetting('Billing', 'FINALIZEZEROAMTINVOICES', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to N (default) then zero amount invoices can not be finalized.'|| chr(10) ||'If set to Y, they can be finalized. The zero amount invoice will get invoicenumber 0 and no AR Transaction is created. This functionality is used for in arear and for in advance invoices. For consolidated invoices invoicenumber is 0 only if consolidated and all child invoices have amount 0.', 'N');
execute CreateSystemSetting('Billing', 'FINANCECHARGEAPPLIESTO', '1', 'I', '1', 'N', 'N', 1, 2, '', '1 = Finance charges are always applied to the bill to customer. This means that they will be assigned to the invoice or statement of the bill to customer. Also if statements are generated per del to customer, all finance charges will appear on the statement of the bill to customer'|| chr(10) ||'2 = Finance charges are applied to the del to customer, with the exception when a bill to customer receives a statement and this statement is for all customers (not per del to). Finance charges will be put on the invoice or statement from the del to customer.', 'N');
execute CreateSystemSetting('Billing', 'FINCHARGEBASEDARBALANCE', '1', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Old method of calculation when past due debits and past due credits are taken into account'|| chr(10) ||'1 = New method of calculation when past due debits and all open credits till sysdate are taken into account', 'N');
execute CreateSystemSetting('Billing', 'FOAPALVALIDATION', '\\', 'S', '\\', 'N', 'N', null, null, '', 'URL for checking the FOAPAL code. Only used for specific interface.', 'N');
execute CreateSystemSetting('Billing', 'FOAPALVALIDATIONRESPONSE', '1000', 'I', '1000', 'N', 'N', 0, 9999, '', 'Maximum time for receiving response in milliseconds.', 'N');
execute CreateSystemSetting('Billing', 'FULLUSEDELIVERYNOTE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Set to Yes when delivery note program is always used.'|| chr(10) ||'Set to No when delivery note program will be not used at all or maybe used partially. '|| chr(10) ||'It does have effect only if SETTLEMENTACTIVE = ''Y''. Else when SETTLEMENTACTIVE = ''N'' the delivery note program must be always used.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTINSURANCEBILLDAY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting determines on which day garment insurance is billed.'|| chr(10) ||'0 = bill on first billing day of the customer.'|| chr(10) ||'1 = bill on first billing day that is a garment delivery day for the customer.  In case none of the garment delivery days is a billing day then garment insurance is billed on first billing day of the customer.'|| chr(10) ||'Note: this setting is only applicable if setting DELIVERYDAYS_US=Y', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMN1', ' ', 'S', ' ', 'N', 'N', null, null, '', 'Used in combination with system setting GARMENTRENTCOLUMNLINE1 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMN2', ' ', 'S', ' ', 'N', 'N', null, null, '', 'Used in combination with system setting GARMENTRENTCOLUMNLINE2 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMN3', ' ', 'S', ' ', 'N', 'N', null, null, '', 'Used in combination with system setting GARMENTRENTCOLUMNLINE3 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMN4', ' ', 'S', ' ', 'N', 'N', null, null, '', 'Used in combination with system setting GARMENTRENTCOLUMNLINE4 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMN5', ' ', 'S', ' ', 'N', 'N', null, null, '', 'Used in combination with system setting GARMENTRENTCOLUMNLINE5 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMNLINE1', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Used in combination with system setting GARMENTRENTCOLUMN1 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMNLINE2', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Used in combination with system setting GARMENTRENTCOLUMN2 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMNLINE3', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Used in combination with system setting GARMENTRENTCOLUMN3 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMNLINE4', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Used in combination with system setting GARMENTRENTCOLUMN4 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GARMENTRENTCOLUMNLINE5', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Used in combination with system setting GARMENTRENTCOLUMN5 for grouping the products of type of merchandise 2 (garments). This grouping will be used in combination with garment rent specification to print more than one garment on the same line on the invoice for a wearer.'|| chr(10) ||'Used in US billing.', 'N');
execute CreateSystemSetting('Billing', 'GEPCHARGELEVEL', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This defines the check to see if the garment emblem protection (GEP) when set is actually active (charged and suppresses emblem charges) for a wearer inventory.  There are 3 options of checks'|| chr(10) ||''|| chr(10) ||'0 only charge if the wearer inventory has an emblem template (default)'|| chr(10) ||'1 only charge if the product list per customer has an emblem template'|| chr(10) ||'2 charge with no checks for emblem template at either wearer inventory or PLPC level', 'N');
execute CreateSystemSetting('Billing', 'GROUPBYROUTEANNIVUPD', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Group customers by route in the log file of anniversary price update scheduled process', 'N');
execute CreateSystemSetting('Billing', 'GROUPELECTRONICPAYMENTS', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This defines if multiple invoices (so multiple credit card transaction records for one customer and create date) are grouped together for one electronic payment transaction or there are separate transactions per invoice.'|| chr(10) ||''|| chr(10) ||'0 = one call to the electronic payment provider per credit card transaction line'|| chr(10) ||'1 = one call to the electronic payment provider per bill to customer and create date in the credit card transaction table', 'N');
execute CreateSystemSetting('Billing', 'INADVANCEPRICEDATE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'The in advance rent price is the price that is active on:'|| chr(10) ||'0 = The invoice period end date (cut off date)'|| chr(10) ||'1 = First day of the in advance rent period', 'N');
execute CreateSystemSetting('Billing', 'INSURANCELOSSWARNING', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1, loss that is included in the insurance is shown on the invoice but not invoiced (meaning not extended).', 'N');
execute CreateSystemSetting('Billing', 'INVAPPTYPECSV', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'Only used for module EXPORTTOCSV. This parameter indicates whether the new invoice appendix type "CSV file" will be available or not. Possible values:'|| chr(10) ||'0 = No CSV export (Default)'|| chr(10) ||'1 = CSV Export with layout LTS', 'Y');
execute CreateSystemSetting('Billing', 'INVCOLLAPSEMODELS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to ''Y'' for wash and rent invoice lines, products with type of merchandise 2 that are models will be collapsed on parent product level on invoice. ', 'N');
execute CreateSystemSetting('Billing', 'INVOICEDATEASSIGNMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Invoice date remains unchanged after changing the route.'|| chr(10) ||'1 = The Invoice date is changed to the new drivingdate after changing the route. The original Invoice Date remains stored.'|| chr(10) ||'Only used for settlement', 'N');
execute CreateSystemSetting('Billing', 'INVOICEFUTUREPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting is only applicable for in advance invoicing. Normally the rent price is determined on the start date of the in advance invoice. However, if a product starts within the in advance period the price cannot be defined on the start date of the invoice period. With this setting to NO the price will be left empty and the row is mentioned in the missing prices. If set to YES then the first future price is used.', 'N');
execute CreateSystemSetting('Billing', 'INVOICEINACTIVECPLPRODUCT', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Rent based on circulating inventory is only charged for products that are active in the CPL.'|| chr(10) ||'1 = Rent based on circulating inventory is charged for products that are active in the CPL or that have become inactive but there is still circulating inventory.'|| chr(10) ||'2 = Rent based on circulating inventory is charged for products that are active in the CPL or that have become inactive but there is still onsite inventory.'|| chr(10) ||'This setting is only applicable for periodical invoicing.', 'N');
execute CreateSystemSetting('Billing', 'INVOICEINACTIVECUSTOMER', '0', 'I', '0', 'N', 'N', 0, 2, '', 'If 0 (default) then no checks are done on date-inactive. The reason is that after the date inactive the customer could have rented merchandise that is invoiced until it is returned.'|| chr(10) ||'f 1 then rent in arrear is invoiced until the date inactive if this is before the cut-off date. For all other invoicelinetypes the cut-off date is used. So if an invoice is generated from 01/08 until 31/08, and the customer has a dateinactive of 15/08, rent in arrear is invoiced until 15/08, but for instance delivery notes from 20/08 are still being invoiced.'|| chr(10) ||'If 2 then all services are invoiced until the date inactive of the customer if this is before the cut-off date. So in the previous example the delivery notes after 15/08 are not invoiced.', 'N');
execute CreateSystemSetting('Billing', 'INVOICEINSURANCEMETHOD', '1', 'I', '1', 'N', 'N', 1, 2, '', '1 = generate garment insurance based on circulating inventory'|| chr(10) ||'2 = generate garment insurance based on max inventory', 'N');
execute CreateSystemSetting('Billing', 'INVOICENRONBAGTAG', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'If this system setting is set to Y then Invoice Number will be printed on customized BagTags. If N, then Customer Number will be printed.', 'N');
execute CreateSystemSetting('Billing', 'INVOICEREPLACEMENTS', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set to N the replacements are not counted by SQ process to be invoiced. '|| chr(10) ||'When set to Y the replacements will be always invoiced.'|| chr(10) ||'NOTE This is for periodical invoicing only', 'N');
execute CreateSystemSetting('Billing', 'INVOICESALESNOTEONDATE', 'N', 'B', 'N', 'N', 'Y', null, null, '', 'When making a direct invoice for a sales note, depending on this setting the user has the possibility to enter a desired invoice date or not. Possible values:'|| chr(10) ||'"N" - The invoice will be created for the system date (default)'|| chr(10) ||'"Y" - The invoice will be created for the desired invoice date  as entered from the user', 'N');
execute CreateSystemSetting('Billing', 'INVOICESUBSTITUTES', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set to N the substitutes are not counted by SQ process to be invoiced. When set to Y the substitutes will be always invoiced (thus rent will be invoiced double in this case: once for the original garment and once for the substitute garment in circulation for customer).', 'N');
execute CreateSystemSetting('Billing', 'INVPRICEDETERMMETHOD', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'This system setting configures if the prices on the periodical invoices are calculated per week or for whole invoiced period.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Price is calculated at the end date of the invoicing period'|| chr(10) ||'1 = Price is calculated for each week of the invoicing period. For each determined price an invoice line is created.'|| chr(10) ||'2 = Determine the wash price and the sales price at the moment of delivery.'|| chr(10) ||''|| chr(10) ||'NOTE: This does not apply to ContainerRent that is always price at the end date of the invoicing period', 'N');
execute CreateSystemSetting('Billing', 'INVVALIDATIONRPTDEVIATION', '100', 'I', '25', 'Y', 'N', 1, 100, '', 'This setting is used for Invoice Validation Report.'|| chr(10) ||'Defines the percentage deviation of the total invoice amount from the average of the last 4 weeks invoices. Overruled by setting it in the selection screen of the report', 'N');
execute CreateSystemSetting('Billing', 'KEEPDETAILEDSQINFO', '999', 'I', '999', 'N', 'N', 6, 999, '', 'It configures the number of weeks for which the status quo items in circulation and status quo sets information is still kept on wearer level - when generated on wearer level only. For status quo''s older than the configured number of weeks the detailed information will be compressed on consumption point level and the information on wearer level will be deleted. ', 'N');
execute CreateSystemSetting('Billing', 'KEEPSQINFO', '999', 'I', '999', 'N', 'N', 52, 999, '', 'It configures the number of weeks for which the status quo information will be still kept in database. '|| chr(10) ||'When the clean up status quo scheduled process is started, the status quo information older than this set number of weeks in the past are cleaned up. ', 'N');
execute CreateSystemSetting('Billing', 'LOSSCHARGEINVENTORYTYPE', '1', 'I', '1', 'N', 'N', 1, 2, '', '1 = Loss charge is based on the circulating inventory.'|| chr(10) ||'2 = Loss charge is based on the max inventory.'|| chr(10) ||''|| chr(10) ||'NOTE: this is for garments only', 'N');
execute CreateSystemSetting('Billing', 'LOSSCHARGEPERCENTAGE', '100', 'I', '100', 'Y', 'N', 1, 999, '3', 'only used if module LOSTCHARGEPERCENTAGE is in the license'|| chr(10) ||'This defines the default value for the percentage of the replacement price that is used for loss charging', 'N');
execute CreateSystemSetting('Billing', 'LOSSFORPOOLDEPARTMENT', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Defines which department is billed for los for pool. '|| chr(10) ||'0 = Department that the item was last seen'|| chr(10) ||'1 = Department to which the item was originally delivered'|| chr(10) ||'In case of on-site inventory scans items might be scanned at another department than they were originally delivered to.', 'N');
execute CreateSystemSetting('Billing', 'LOSSFORPOOLMETHOD', '2', 'I', '2', 'N', 'N', 1, 2, '', 'This setting determines how the cut off date for the loss calculation is determined.'|| chr(10) ||'1 = Invoice Period  -  Cut off date is defined per invoice period per invoice frequency'|| chr(10) ||'2 = Number of days  - Number of days is defined in product list per customer with a default defined at customer level.'|| chr(10) ||'Only used in the module LOSSFORPOOL.', 'N');
execute CreateSystemSetting('Billing', 'LOSSFORPOOLPRICE', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting defines which price is billed for unreturned pool items.'|| chr(10) ||'1 =  Full replacement price to charge loss for pool'|| chr(10) ||'2 =  Residual value (replacement price multiplied with the residual value percentage). The residual value percentage is based on the residual value scheme defined in product list per customer.'|| chr(10) ||'This setting is only used in the module LOSSFORPOOL.', 'N');
execute CreateSystemSetting('Billing', 'MANUALINVOICEBUSINESSUNIT', '0', 'I', '0', 'N', 'N', 0, 3, '', 'Determine how the invoice business unit is determined for a manual invoice:'|| chr(10) ||'0 = Take the invoice business unit from the debtor'|| chr(10) ||'1 = Take the current business unit in which the invoice is created'|| chr(10) ||'2 = If 0 and 1 are different then the user must chose'|| chr(10) ||'3 = Use the invoice business unit from the del to customer'|| chr(10) ||''|| chr(10) ||'NOTE: if value 0, 1 or 2 then manual invoices created via the switchboard will always use the invoice business unit from the debtor (value 0) regardless of this system setting', 'N');
execute CreateSystemSetting('Billing', 'MANUALINVOICEDATECONTROL', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if you are allowed to add a manual invoice with an invoice date before system date.'|| chr(10) ||'This also applies in modify mode where you cannot adjust the invoice date before the creation date'|| chr(10) ||''|| chr(10) ||'0 = Allowed'|| chr(10) ||'1 = Not Allowed', 'N');
execute CreateSystemSetting('Billing', 'MANUALINVOICEDATELIMIT', '0', 'I', '0', 'N', 'N', 0, 99, '2', 'This controls how many days ahead of system date you are allowed to create a manual invoice'|| chr(10) ||'This also applies in modify mode where you cannot change the invoice date to more than creation date plus this number of days'|| chr(10) ||''|| chr(10) ||'0 = no checks, any future dates allowed'|| chr(10) ||'>0 = limit on future dates', 'N');
execute CreateSystemSetting('Billing', 'MANUALINVOICEVALUECONTROL', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if you are allowed to create a manual invoice with a negative total amount (PreBillAmount).'|| chr(10) ||'The check is on save of the invoice (add or modify), not per line'|| chr(10) ||''|| chr(10) ||'0 = Allowed'|| chr(10) ||'1 = Blocked', 'N');
execute CreateSystemSetting('Billing', 'MAXDISCOUNTCASHAPPL', '0.5', 'F', '0.5', 'N', 'N', 0, 9999, '', 'Cash application: Defines the maximum amount the user can enter as discount in the cash application screen.', 'N');
execute CreateSystemSetting('Billing', 'MGCRESVALUECHANGEREASON', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting is used to control whether an authorized system user has to fill in a specific reason code when he/she changes the residual value % column on the Residual Value tab in the Maintain garment Charges form.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not allow to enter a specific reason code'|| chr(10) ||'1 - User must select a specific reason code', 'N');
execute CreateSystemSetting('Billing', 'MINIMUMINVOICEAMTPDA', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting controls whether it is allowed to credit more on the PDA than would normally be allowed since it exceeds the minimum invoice amount as defined for the customer. Possible values:'|| chr(10) ||'1 = Allow crediting below minimum (default)'|| chr(10) ||'2 = Don not allow crediting below minimum'|| chr(10) ||''|| chr(10) ||'When set to 2, when generating a direct invoice, then always a minimum invoice line amount is created for those customers that have a minimum invoice amount defined, even when the mimimum amount does not have to be applied (minimum charge will be 0).'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when US direct invoicing is used, system setting SETTLEMENTACTIVE= ''Y'' and the ABS RouteAssistant is used for settlement. ', 'N');
execute CreateSystemSetting('Billing', 'MININVOICEAMNTTOBEREACHED', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'When set, the user may define a minimum invoice amount to be reached. This means that if the invoice amount is smaller than this defined min amount then the invoice is not created (only applicable for periodical invoices since only these invoices you can regenerate later on and have a bigger invoice amount since in the meantime rent or services have to be invoiced also.)', 'N');
execute CreateSystemSetting('Billing', 'MININVOICEAMOUNTRULE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Minimum invoice amount is not added when the number of invoicelines that are subject to minimum is 0. So only when there is at least one invoice line subject to minimum and the invoice amount is less than the minimum.'|| chr(10) ||'1 = Minimum invoice amount is not added when the number of invoicelines that are subject to minimum is 0 or if the sum of the amounts of the invoicelines that are subject to minimum is 0.', 'N');
execute CreateSystemSetting('Billing', 'MINRENTRETURNRENTPRIORITY', '1', 'I', '1', 'N', 'N', 1, 3, '', 'This setting controls whether any Return Rent should be charged when a customer is setup for both Min Rent and Return Rent calcuation and both methods would be applicable for a certain period of time. Possible values:'|| chr(10) ||'1 = Charge only Min Rent when Min Rent and Return Rent weeks overlap'|| chr(10) ||'2 = Charge both Min Rent and Return Rent when Min Rent and Return Rent weeks overlap'|| chr(10) ||'3 = Start charging Return Rent after the Min Rent period ends when Min Rent and Return Rent weeks overlap'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module RENTBASEDONRETURNWEEKS is in the license and can only be used in combination with EU invoicing.', 'N');
execute CreateSystemSetting('Billing', 'MISCCHARGEREASON', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Reason code can not be entered for a miscellaneous charge'|| chr(10) ||'1 = Reason code can be entered for a miscellaneous charge but can be left empty.'|| chr(10) ||'2 = Reason code must be entered for a miscellaneous charge (mandatory)', 'N');
execute CreateSystemSetting('Billing', 'NETPRICEONINVOICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set the price for rent, wash and weight invoice lines will have the discount subtracted, resulting in a net price. ', 'N');
execute CreateSystemSetting('Billing', 'NONGARMENTSLOSSCHARGE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Loss charges are always calculated for non garments, so disregarding the setting on customer level (Charge loss charge in garment charges tab).'|| chr(10) ||'1 = Loss is charged for non garments depending on the setting on customer level.'|| chr(10) ||''|| chr(10) ||'As of release 9.04.03 this setting is no longer used and only the customer settings are taken into account since there are separate settings for garments and non-garments now.', 'N');
execute CreateSystemSetting('Billing', 'NORENTONDELIEVERYSTOP', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If Y and consumption point logistics has a week stop, fix rent qty is not billed', 'N');
execute CreateSystemSetting('Billing', 'NSFFEE', '0.00', 'F', '0.00', 'N', 'N', 0, 9999, '', 'Amount of money that is charged automatically as NSF fee when in the reverse payment function in the cash application dialog the checkbox Charge NSF fee is checked.'|| chr(10) ||'Amount of money is in currency of the country of the plant.', 'N');
execute CreateSystemSetting('Billing', 'ONLYEMAILADJUSTED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Y = only invoices with adjustments will be sent by e-mail or fax after complete settlement.'|| chr(10) ||'N = all invoices (adjusted or not) will be sent by e-mail or fax after complete settlement'|| chr(10) ||'This setting replaces the ONLYEMAILFAXADJUSTED system setting as of 9.05.03.', 'N');
execute CreateSystemSetting('Billing', 'ONLYEMAILFAXADJUSTED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Y = only invoices with adjustments will be sent by e-mail or fax after complete settlement.'|| chr(10) ||'N = all invoices (adjusted or not) will be sent by e-mail or fax after complete settlement'|| chr(10) ||'This setting is replaced by the ONLYEMAILADJUSTED system setting as of 9.05.03.', 'N');
execute CreateSystemSetting('Billing', 'ONLYMINAMOUNTINVOICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if minimum invoice amount should be generated if the only charge is the minimum invoice amount.'|| chr(10) ||'If set to Yes then the invoice is generated for only the minimum, else no minimum invoice line is '|| chr(10) ||'created but still an invoice is created (with zero amount).'|| chr(10) ||''|| chr(10) ||'The system should look at the sum of the extended amounts to be 0 or not.'|| chr(10) ||'4 situations:'|| chr(10) ||'Sum 	Systemsetting	Result'|| chr(10) ||'0	N		do not generate the min.amount invoice line, but DO generate the invoice'|| chr(10) ||'0	Y 		generate min.invoice amount line'|| chr(10) ||'>0	don''t care	                generate min.invoice amount line'|| chr(10) ||'<0	don''t care	do not generate the min.amount invoice line, but DO generate the invoice', 'N');
execute CreateSystemSetting('Billing', 'OVERPAYDISCOUNTLEVEL', '1', 'F', '1', 'N', 'N', 0, 100, '', 'Cash application: Defines the maximum amount to which an overpayment can be booked as discount.', 'N');
execute CreateSystemSetting('Billing', 'PACKINGNOTEOBLIGATED', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'When set to NO the Gen. Del. Docs button in the Route Status Control Screen is enabled no matter what the status of the packing note generation is. So for pure garment plants this setting should be set to No.'|| chr(10) ||'When set to YES te Gen.Del.Docs button in only active when packingnotes are generated.', 'N');
execute CreateSystemSetting('Billing', 'PLANTINFOATASCIIINVOICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines for ASCII printed invoices if the plant information (name and address and phone#) should be printed. Set to N when this information is preprinted.', 'N');
execute CreateSystemSetting('Billing', 'PLANTINFOATASCIISTATEMENT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines for ASCII printed statements if the plant information (name and address) will be printed.'|| chr(10) ||'Set to N when this information is preprinted.', 'N');
execute CreateSystemSetting('Billing', 'PRICEINDEXCODEOBLIGATED', '0', 'I', '1', 'N', 'N', 0, 1, '', 'This setting controls whether it is obligated to fill in a price index code for a general price list. This setting will also be used from within the Price update per chain dialog. Possible values:'|| chr(10) ||'0 = Price index code is optional'|| chr(10) ||'1 = Price index code is obligated', 'N');
execute CreateSystemSetting('Billing', 'PRICELISTMAINTBYUSERGROUP', '0', 'I', '0', 'N', 'Y', 0, 1, '', 'This setting controls if it will be optional or mandatory to define a maintenance usergroup for a general price list. Possible values:'|| chr(10) ||'0 - The checkbox <Only maintained by> within the general price list is not marked'|| chr(10) ||'1 - The checkbox <Only maintained by> within the general price list is marked automatically'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the PRICELISTUSERGROUPACCESS module is in the license', 'N');
execute CreateSystemSetting('Billing', 'PRINTINVOICEMETHOD', '1', 'I', '1', 'N', 'N', 1, 2, '', '1= With all features (default)'|| chr(10) ||'2= Fast printing, without the following features:'|| chr(10) ||'    - possibillity to print invoice appendixes'|| chr(10) ||'    - PDF export (fax and e-mail functionallity)'|| chr(10) ||'    - multiple invoice copies'|| chr(10) ||'    - printing in (foreign) customers language.'|| chr(10) ||' ', 'N');
execute CreateSystemSetting('Billing', 'PRINTINVSEQUENCE', '0', 'I', '0', 'N', 'N', 0, 5, '', 'Invoices are printed in sequence of:'|| chr(10) ||'0 = Invoice Number'|| chr(10) ||'1 = Del to Customer number'|| chr(10) ||'2 = Bill to CustomerNumber, Del to CustomerNumber'|| chr(10) ||'3 = LegacyCustomerNumber, Del to CustomerNumber'|| chr(10) ||'4 = Bill to CustomerLegalName'|| chr(10) ||'5 = Bill to CustomerLegalName, Del to CustomerNumber', 'N');
execute CreateSystemSetting('Billing', 'PRINTRECEIPTDIRECTINV', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When this setting is set to Y then for every Direct Invoice (EU) report a Receipt report is printed (only when there is no preview).', 'N');
execute CreateSystemSetting('Billing', 'PRINTSEPARATORSHEET', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Is giving the default value for printing separator sheet while printing (consolidated) invoices.', 'N');
execute CreateSystemSetting('Billing', 'PROCESSLOSSINSETTLEMENT', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This system setting has effect only in complete settlement and cancelling loss in loss charge monitor. '|| chr(10) ||'During settlement, when loss lines are charged, the unique items can be automatically ragged or set to COG based on the value of this system setting.'|| chr(10) ||'Possible values: '|| chr(10) ||'0 = No action'|| chr(10) ||'1 = Automatic rag lost items'|| chr(10) ||'2 = Automatic set to COG (Customer Owned) lost items.'|| chr(10) ||''|| chr(10) ||'Note: When a grace period is set, then items are always made COG disregarding this setting.'|| chr(10) ||'Note: This is also taken into account in cancelling loss charges in the loss charge monitor', 'N');
execute CreateSystemSetting('Billing', 'PROCESSLOSSMANUALINVOICE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = When creating a manual invoice and credit loss, loss will be charged again on the next invoice.'|| chr(10) ||'1 = When creating a manual invoice and credit loss, loss will not be charged again on the next invoice. Only when using the credit invoice or credit invoice line it will be charged again.'|| chr(10) ||'This setting is only used in combination with settlement.', 'N');
execute CreateSystemSetting('Billing', 'REASONCODEFORAUTOBILLING', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when automatically creating a positive rental quantity adjustment when the expiration date of the sample period has passed. From that moment on the sample should be treated as a regular rental product and therefore being charged against the normal price. Only reason codes should be selected that are defined as inventory adjustment reason for "Linen".'|| chr(10) ||''|| chr(10) ||'This setting is only of any importance when the module SAMPLE is in the license of the plant. It will be used as a trigger in a scheduled process to automatically create (negative) rental quantity adjustments for sample products that have expired.', 'N');
execute CreateSystemSetting('Billing', 'REASONCODEFORBM6CIRCINV', '-', 'S', '-', 'N', 'N', null, null, '', 'Reason code used when automatically creating rental quantity adjustments for changes to circulating inventory in Billing Method 6', 'N');
execute CreateSystemSetting('Billing', 'REASONCODESAMPLEPERIOD', '-', 'S', '-', 'N', 'N', 1, 6, '', 'Reason code used when automatically creating a negative rental quantity adjustment when the expiration date of the sample period has passed. Only reason codes should be selected that are defined as inventory adjustment reason for "Linen".'|| chr(10) ||''|| chr(10) ||'This setting is only of any importance when the module SAMPLE is in the license of the plant. It will be used as a trigger in a scheduled process to automatically create (negative) rental quantity adjustments for sample products that have expired.', 'N');
execute CreateSystemSetting('Billing', 'RECHARGELOSSAFTERCREDIT', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 : Only for full credited invoice lines the ChargedForLoss flag is set back to N'|| chr(10) ||'1 : For all invoice lines (including partly credited) the ChargedForLoss flag is set back to N.'|| chr(10) ||'2 : The ChargedForLoss flag is not set back to N. Loss will not be invoiced again after it has been credited.'|| chr(10) ||''|| chr(10) ||'This setting is only applicable when SETTLEMENTACTIVE = Y.'|| chr(10) ||'and from 9.05.02 for Garments only', 'N');
execute CreateSystemSetting('Billing', 'RECHARGELOSSAFTERCREDITNG', '0', 'I', '0', 'N', 'N', 0, 2, '0', 'This setting controls if NON GARMENT loss charge invoices lines that are credited on the RA will be charged again or not.'|| chr(10) ||''|| chr(10) ||'If an invoice line is full credited'|| chr(10) ||'   0 = do not set the returned value so loss charges will be raised again'|| chr(10) ||'   1 = do not set the returned value so loss charges will be raised again'|| chr(10) ||'   2 = set the returned value so loss charges will not be raised again'|| chr(10) ||'If an invoice line is partially credited'|| chr(10) ||'   0 = set the returned value so loss charges will not be raised again'|| chr(10) ||'   1 = set the returned value so loss charges will be raised again for the quantity credited'|| chr(10) ||'   2 = set the returned value to total value so loss charges will not be raised again'|| chr(10) ||''|| chr(10) ||''|| chr(10) ||'This setting is only applicable when SETTLEMENTACTIVE = Y.', 'N');
execute CreateSystemSetting('Billing', 'REMITBATCHPAYMENTTYPE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No paymenttype per remit batch'|| chr(10) ||'1 = Paymenttype can be specified on a remit batch (optional)'|| chr(10) ||'2 = Paymenttype must be specified on a remit batch (mandatory)'|| chr(10) ||'If a paymenttype is specified all the remittances in the remit batch will inherit the paymenttype. It is not possible to overwrite the paymenttype on the remittance,', 'N');
execute CreateSystemSetting('Billing', 'RENTALCHARGEFORLOSTGRMT', 'N', 'B', 'N', 'N', 'N', null, null, '', 'During the invoice generation the lost charges will be calculated. For every invoice line of type loss there will be an invoiceline Rent with subtype Rental Charge For Lost Garments (Rental Reduction) with the same quantity as the lost billed quantity, the rental price and an amount of billed qty * rent price. '|| chr(10) ||'This ss is enabling or disabling the usage of Rental Charge For Lost Garments'|| chr(10) ||''|| chr(10) ||'NOTE: system setting InsuranceLossWarning should be on 1 for this to work', 'N');
execute CreateSystemSetting('Billing', 'RESTRICTINVOICEDATE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This setting will be used to prevent that users can finalize invoices with an invoice date before the current month because those invoices may cause problems in the interface with a bookkeeping system. Possible values:'|| chr(10) ||'N = There is no restriction for the invoice date'|| chr(10) ||'Y = Invoice dates that are before the current month are not accepted so the date must be within the current month or later.'|| chr(10) ||'The setting will be taken into account at the moment of finalizing an invoice, except for manual invoices. For manual invoices another system setting is used (ALLOWMANUALINVOICEDATE).', 'N');
execute CreateSystemSetting('Billing', 'ROUNDTOTALAMNTINVOICE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'For all Swiss customers it is a common use that the end sum of the invoices will be rounded on 0,05.'|| chr(10) ||'Rouding differences must be booked on a pre-defined turnovergroup.', 'Y');
execute CreateSystemSetting('Billing', 'ROUNDTOTALINVOICEAMNT', '0', 'I', '0', 'Y', 'N', 0, 3, '', 'At the end sum of the invoices will be rounded depending on:'|| chr(10) ||'0 = no rounding'|| chr(10) ||'1 = round to 5 cents (to x.x5 or to x.x0)'|| chr(10) ||'2 = round to 0 cents (to x.00)'|| chr(10) ||'3 = round to to the nearest number that is dividable by 5 (no decimals). '|| chr(10) ||''|| chr(10) ||'Rouding differences must be booked on a pre-defined turnovergroup.', 'N');
execute CreateSystemSetting('Billing', 'SETPRICEPERCHANGE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'N = Price for the whole set  (default)'|| chr(10) ||'Y = Price per change, price is multiplied with number of changes.'|| chr(10) ||'System setting is only applicable for periodical invoicing for rent for billingmethod 1. In case the setting is Y then multiply the price not only with number of wearers - as it is done when system setting is N -, but also with number of changes for calculating the invoiceline.amount.', 'N');
execute CreateSystemSetting('Billing', 'SETTLEMENTACTIVE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set then settlement procedure is active. Typical use: Y in US, N in EU.', 'N');
execute CreateSystemSetting('Billing', 'SETTLEMENTADJDELIVERQTY', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to ''Y'' the user can adjust manually the delivered quantity in settlement for wash, rent and sales invoice lines. '|| chr(10) ||'When set to ''N'' delivered quantity of the invoice line (wash, rent or sales) is adjusted automatically with the same value as the adjusted billed quantity.', 'N');
execute CreateSystemSetting('Billing', 'SETTLEMENTAUTORECALC', 'N', 'B', 'N', 'N', 'N', null, null, '', 'For YES : Automatically recalculate taxes and special charges and invoice minimums in settlement'|| chr(10) ||'For NO: Do not recalculate taxes/specail charges/min inv amount in settlement', 'N');
execute CreateSystemSetting('Billing', 'SHOWVATONCONDCOSTREP', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set the VAT and Gross Amounts are also shown in Condensed Cost Report. ', 'N');
execute CreateSystemSetting('Billing', 'SIZEBILLINGGROUPPRICECTL', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls the relationship between standard and surcharge size billing groups when deleting prices'|| chr(10) ||''|| chr(10) ||'0 = Default - no controls'|| chr(10) ||'1 = You cannot delete an individual size billing group surcharge price (so not the standard one) on its own, you must delete the standard (or NULL group one) of the same date and this cascades a delete to the surcharge price ones.'|| chr(10) ||''|| chr(10) ||'NOTE: the "standard" price can either have a size billing group that is flagged as the standard one OR have a size billing group of NULL'|| chr(10) ||'NOTE: the cascade delete will remove all prices of the same date, price list, product, size, type etc with size billing groups set that are not the "standard" one', 'N');
execute CreateSystemSetting('Billing', 'SIZESPECIALCHARGEOPTIONS', '0', 'I', '0', 'N', 'N', 0, 7, '', '0 - no special prices are used '|| chr(10) ||'1 - special prices for Rent'|| chr(10) ||'2 - special prices for Sales'|| chr(10) ||'3 - special prices for Replacement'|| chr(10) ||'4 - special prices for Rent and Sales'|| chr(10) ||'5 - special prices for Rent and Replacement'|| chr(10) ||'6 - special prices for Sales and Replacement'|| chr(10) ||'7 - special prices for Rent, Sales and Replacement', 'N');
execute CreateSystemSetting('Billing', 'SPECCHARGEPRINTEDNOTE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Special charge per finalized delivery note is calculated per delivery note'|| chr(10) ||'1 = Special charge per finalized delivery note is calculated per delivery day.', 'N');
execute CreateSystemSetting('Billing', 'SPECIALCHARGE', 'EU', 'S', 'EU', 'N', 'N', null, null, '', 'Used for defining the frequency with which a special charge applies to an invoice. '|| chr(10) ||'Allowed values:'|| chr(10) ||'EU'|| chr(10) ||'US', 'Y');
execute CreateSystemSetting('Billing', 'SPECIALCHARGEDELPIECERENT', 'N', 'B', 'N', 'N', 'N', null, null, 'YN', 'Depending on this setting the calculation of the special charge per delivered pieces is either based on the delivered pieces for which "wash" invoice lines have been created, or it is based on all delivered products. In the latter case the delivered quantities will be taken directly from the delivery notes that are linked to the invoice, independent of the billing method. It should be applied to both LOG and COG products.'|| chr(10) ||'Possible values:'|| chr(10) ||'N - Special charge per delivered piece is calculated only over delivered products on invoice lines of type "Wash".'|| chr(10) ||'Y - Special charge per delivered piece is calculated over all delivered products, independent of their billing method or ownership. So it should be applied to both LOG and COG.', 'N');
execute CreateSystemSetting('Billing', 'SPECIALINVPRINTANDPROCESS', '1', 'I', '1', 'N', 'N', 1, 3, '', 'Sets the default value for printing and process a special invoice in the special order screen. Possible values are: '|| chr(10) ||'1 = Print invoice and packing note'|| chr(10) ||'2 = Print invoice and process delivery note immediately'|| chr(10) ||'3 = Print and process delivery note and create test invoice', 'N');
execute CreateSystemSetting('Billing', 'SPLITSOILTICKETS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y the soil tickets will be split up per soil receiving department defined on product group level. It works only for Soil Tickets generated in the same time with direct invoices US.', 'N');
execute CreateSystemSetting('Billing', 'SQINACTIVEPLPC', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is applicable both for SQ items in circulation and SQ mats in circulation.'|| chr(10) ||'0 = All items are processed, also with inactive PLPC. When PLPC is inactive the billing method from the last (last dateinactive) PLPC is taken.'|| chr(10) ||'1 = All items are processed, also with inactive PLPC. When PLPC is inactive update Rent Other'|| chr(10) ||'2 = Process only items with active PLPC.'|| chr(10) ||'In case of mats in circulation option 0 and 1 are the same.', 'N');
execute CreateSystemSetting('Billing', 'SQONWEARERLEVEL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If ''Y'' then Status Quo Items in Circulation data should be stored besides on consumptionpoint level, also on wearer (employment) level. Advantage more detailed information, Disadvantage: Status Quo Items in Circulation processing will take longer.', 'N');
execute CreateSystemSetting('Billing', 'SQSETCOMPRESSSIZES', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This system setting compresses SQSetsInCirculation records on size *: if an active product list per customer with size * exists, then all sizes will be compressed for size *', 'N');
execute CreateSystemSetting('Billing', 'SQSETONWEARERLEVEL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If ''Y'' then Status Quo Sets data should be stored besides on consumptionpoint level, also on wearer (employment) level. Advantage more detailed information, Disadvantage: Status Quo Sets processing will take longer.'|| chr(10) ||'Used esspecially for invoicing in advance.', 'N');
execute CreateSystemSetting('Billing', 'SRCHARGEPERCENTAGE', '100', 'I', '100', 'Y', 'Y', 1, 999, '3', 'only used if module SRCHARGEPERCENTAGE is in the license'|| chr(10) ||'This defines the default value for the percentage of the replacement price that is used for systematic replacement charging', 'N');
execute CreateSystemSetting('Billing', 'STATEMENTEMAILANDPRINT', '1', 'I', '1', 'N', 'N', 1, 2, '', '1 = When (re)printing statements also statements are printed for customers where the statement is send to by e-mail.'|| chr(10) ||'2 = When (re)printing statements statements are skipped (not printed) for customers where the statement is send to by e-mail.', 'N');
execute CreateSystemSetting('Billing', 'STATEMENTSORTING', '1', 'I', '1', 'Y', 'N', 1, 6, '', 'Generate Statements: Defines the default way in which order statements should be printed.:'|| chr(10) ||'1 = Customer number'|| chr(10) ||'2 = Customer name (affects also Report AR Trial balance sorting)'|| chr(10) ||'3 = Zip code'|| chr(10) ||'4 = Route/Day/Stop'|| chr(10) ||'5 = Chain/Customer number'|| chr(10) ||'6 = Chain/Customer name', 'N');
execute CreateSystemSetting('Billing', 'STORETESTINVINVOICEJOB', 'N', 'B', 'N', 'Y', 'N', null, null, 'Y;N', 'If ''Yes'', then test invoices created during invoice job process are stored in the database. If ''No'', then they are not stored.', 'N');
execute CreateSystemSetting('Billing', 'TAXDEFINITION', 'EU', 'S', 'EU', 'N', 'N', null, null, '', 'Used for defining taxes at tax group level. For EU the taxes will be defined at tax group level, for US they will be defined at state/county/city level.'|| chr(10) ||'Values: EU'|| chr(10) ||'             US', 'N');
execute CreateSystemSetting('Billing', 'UNDERUSEMETHOD', '1', 'I', '1', 'N', 'N', 1, 5, '', 'This setting is only used in module UNDERUSE.'|| chr(10) ||'1 = Monthly underuse calculation'|| chr(10) ||'2 = Weekly underuse calculation (used in UK).'|| chr(10) ||'3 = Weekly periodic, multiply the minimum delivery with the number of weeks in the invoice period.'|| chr(10) ||'4 = Weekly underuse calculation for linen and garments'|| chr(10) ||'5 = Weekly underuse calculation (used in France)', 'N');
execute CreateSystemSetting('Billing', 'USBILLTOADDRESS', '1', 'I', '1', 'N', 'N', 1, 2, '', 'Only applicable for US direct invoicing'|| chr(10) ||'Defines where the invoice is addressed to:'|| chr(10) ||'1= Visit address of del-to customer  '|| chr(10) ||'2= Invoice address of bill-to customer', 'N');
execute CreateSystemSetting('Billing', 'USEHANDHELDFORRA', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'Setting for use handheld terminal for route accounting', 'Y');
execute CreateSystemSetting('Billing', 'USELEGALNAMEBILLTO', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Depending on this system setting the legal name or the name of the bill to customer will be printed on the invoice. When setting is Y the legal name will be printed, else the name.', 'N');
execute CreateSystemSetting('Billing', 'USELEGALNAMEBILLTOSTATEM', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Depending on this system setting the legalname or the name of the bill to customer will be printed on the statement. When setting is Y the legalname will be printed, else the name.', 'N');
execute CreateSystemSetting('Billing', 'USELEGALNAMEDELTO', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Depending on this system setting the legalname or the name of the deliver to customer will be printed on the invoice. When setting is Y the legalname will be printed, else the name.', 'N');
execute CreateSystemSetting('Billing', 'USELEGALNAMEDELTOSTATEM', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Depending on this system setting the legalname or the name of the deliver to customer will be printed on the statement. When setting is Y the legalname will be printed, else the name.', 'N');
execute CreateSystemSetting('Billing', 'USELOSSWARNPERIODENDCUST', '0', 'I', '0', 'N', 'N', 0, 3, '', '0 = Use Loss warn period (use as is functionality)'|| chr(10) ||'1 = When customer is ended, loss charges for garments and non garments will be charged without a loss warn period.'|| chr(10) ||'2 = When customer is ended, loss charges for garments only will be charged without a loss warn period.'|| chr(10) ||'3 = When customer is ended, loss charges non garments only will be charged without a loss warn period.', 'N');
execute CreateSystemSetting('Billing', 'USETURNOVERGROUP', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if turn-over groups are defined in ABSSolute (Y) or only in a third party booking system (N).', 'N');
execute CreateSystemSetting('Billing', 'VERTEXTAXCOMPANY', '-', 'S', '-', 'N', 'N', null, null, '', 'Company code used for Vertex Tax calculations', 'N');
execute CreateSystemSetting('Billing', 'VERTEXTAXSECURITY', '-', 'S', '-', 'N', 'N', null, null, '', 'trusted ID used for certification of the web service call to Vertex', 'N');
execute CreateSystemSetting('Billing', 'VERTEXTAXURL', '-', 'S', '-', 'N', 'N', null, null, '', 'this is the url used to connect to the vertex tax service', 'N');
execute CreateSystemSetting('Billing', 'WARNLOSSPERIOD', '0', 'I', '1', 'N', 'N', 0, 1, '', '0 = Warning period is number of weeks between invoice date and inactive < number of warning weeks then loss is not extended on the invoice.'|| chr(10) ||'1 = Warning period is number of weeks between invoice date and inactive <= number of warning weeks then loss is not extended on the invoice.', 'N');
execute CreateSystemSetting('Billing', 'WASHONWEARERLEVEL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'This system setting applies only for direct invoices US. When set and the garment rent specification of the customer is 1 (products per wearer) then also the wash lines will be on wearer level - only for non pool uniquely coded delivered items that are billed for wash. ', 'N');
execute CreateSystemSetting('Billing', 'WEEKSLOSSGRACEPERIOD', '0', 'I', '0', 'N', 'N', 0, 52, '', 'Number of weeks of grace period. If an item that has been charged for loss, is returned by the customer within the grace period, it is credited. Grace period can only be used in combination with charging loss. Value 0 means no grace period.', 'N');
execute CreateSystemSetting('Billing', 'WEEKSWARNLOSSCHARGE', '2', 'I', '2', 'N', 'N', 0, 999, '', 'Loss charges are billed after WEEKSWARNLOSSCHARGE number of weeks', 'N');
execute CreateSystemSetting('Billing', 'WEEKSWARNLOSSCHARGENONG', '2', 'I', '2', 'N', 'N', 0, 999, '', 'Loss charges for non garments are billed after WEEKSWARNLOSSCHARGENONG number of weeks', 'N');
execute CreateSystemSetting('Billing', 'WEEKSWARNLOSSCHARGESPLIT', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Use WEEKSWARNLOSSCHARGEsetting for both garments and non garments. '|| chr(10) ||'1= Use WEEKSWARNLOSSCHARGEsetting for garments only and WEEKSWARNLOSSCHARGENONG for non garments.', 'N');
execute CreateSystemSetting('Billing', 'ZEROAMOUNTINVOICELINES', '1', 'I', '1', 'N', 'N', 1, 3, '', '1 : Zero line will be created, and will always stay on the invoice (but maybe not printed)'|| chr(10) ||'2 : Zero lines are deleted during finalizing the invoice (note: this is invoice finalisation, not settlement)'|| chr(10) ||'3 : Zero lines are NOT created during invoice generation'|| chr(10) ||'(Remind : A zero line has price zero, a missing price is not a zero price)', 'N');
execute CreateSystemSetting('Billing', 'ZEROMISCCHARGETURNOVER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls if its only possible to define a turnover group for a miscellaneous charge when it has value > 0, or also when it concerns a miscellaneous charge with a zero value (regardless of the fact if it has a price 0 or a quantity 0).'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not allow to define a turnover group when the amount is 0'|| chr(10) ||'1 - Do allow to define a turnover group when the amount is 0'|| chr(10) ||'This setting is only relevant when system setting USETURNOVERGROUP = Y. Default value is 0, which implies that by default it is not possible to define a turnover group for a miscellaneous charge with a zero amount.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ACTIVATEMAINORDER', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it will be possible to define an expected delivery date and a main order cutoff date for a customer or not. These dates will be used to determine the expected fulfillment date when generating a garment order via the web portal. Possible values:'|| chr(10) ||' 0 - Do not show these date fields (default)'|| chr(10) ||' 1 - Do show these date fields'|| chr(10) ||''|| chr(10) ||'The field is only relevant when the module BKLINTERNETMAINORDERS is in the license', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ALLOWAUTOMATICSALES', 'N', 'B', 'N', 'Y', 'Y', null, null, '', 'Default value for flag automatic sales on Garment tab. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ALLOWREPAIR', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Used for residential services:'|| chr(10) ||'0 = Repair not allowed (for all clients)'|| chr(10) ||'1 = Repair allowed (for all clients)'|| chr(10) ||'2 = Repair allowed defined per client.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ANNIVERSARYPRICEADJ', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Contract screen: Default value for the field Anniversary price adjustment in the contract screen inside the customer screen.'|| chr(10) ||'Options:'|| chr(10) ||'1- no anniversary price adjustments'|| chr(10) ||'2- automatic priced adjustment a anniversary date of contract'|| chr(10) ||'3- signal only that anniversary date is imminent', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BANKACCOUNTOBLIGATED', '9', 'I', '9', 'N', 'N', 1, 9, '', '1 = Not visible'|| chr(10) ||'2 = Visible, not obligated'|| chr(10) ||'3 = Obligated'|| chr(10) ||'4 = Only enabled and obligated for payment acceptgiro (5)'|| chr(10) ||'5 = Only enabled and obligated for payment automatic collection (6)'|| chr(10) ||'6 = Only enabled and obligated for payment acceptgiro and automatic collection'|| chr(10) ||'7 = Enabled, only obligated for payment acceptgiro'|| chr(10) ||'8 = Enabled, only obligated for payment automatic collection'|| chr(10) ||'9 = Enabled, obligated for payment acceptgiro and automatic collection'|| chr(10) ||'Please note: combination of BANKINSTITUTION = YES and value 1 is obsolete. The systemsetting BANKINSTITUTION is not necessary anymore, but is kept for backward compatibility and for other dialogs.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BANKINSTITUTION', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If this setting is put on ''Y'' then in billing EU tab ''bank institution'' field should be filled. Bank institution is needed when using automatic collection as payment method.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BILLINGTAB', '1', 'I', '1', 'N', 'N', 0, 2, '', 'Billing-tab: Defines if the billing tab in the customer form should be '|| chr(10) ||'0=No billing done with ABSSolute'|| chr(10) ||'1=EU-style'|| chr(10) ||'2=US-style', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BPAUTOSETPLPCFROMCUST', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls what happens to budget protection settings at PLPC level if you change it at customer level'|| chr(10) ||''|| chr(10) ||'0 = if you switch a budget protection attribute on at customer level, all relevant products get this attribute switched on at PLPC level (relevant means you could enable it manually)'|| chr(10) ||''|| chr(10) ||'1 = if you switch a budget protection attribute on at customer level, all relevant products get this attribute enabled but NOT switched on at PLPC level (relevant means you could enable it manually)'|| chr(10) ||''|| chr(10) ||'Regardless of this setting, if you switch OFF a Budget Protection attribute at Customer level from the customer dialog or using contract compliancy enforce, it will be switched OFF for all products on PLPC level', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BPGARMENTEMBLEMPROTECTION', 'N', 'B', 'N', 'N', 'N', null, null, '', 'makes the GEP (Garment Emblem insurance) option visible'|| chr(10) ||''|| chr(10) ||'Y = Visible'|| chr(10) ||'N = default = hidden', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BUDGETPROTECTIONDEFAULT', 'NNNNNNNN', 'S', 'NNNNNNNN', 'Y', 'N', 8, 8, 'YN', 'String that holds default values for the various Budget Protection types. Each position in the string represents the default value to be taken for that type of Budget Protection, in order:'|| chr(10) ||'1 - Material Maintenance Protection (MMP)'|| chr(10) ||'2 - Garment Setup Protection (GSP)'|| chr(10) ||'3 - Garment Maintenance Protection (GMP)'|| chr(10) ||'4 - Garment Loss Protection (GLP)'|| chr(10) ||'5 - Garment Repair Protection (GRP)'|| chr(10) ||'6 - Garment Emblem Protection (GEP)'|| chr(10) ||'7 - Merchandise Buyout Protection (MBYOP)'|| chr(10) ||'8 - Material Loss Protection (MLP)'|| chr(10) ||''|| chr(10) ||'for example NNYNNNNN means only GMP will be defaulted as Y', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'BUDGETPROTECTIONGLPPERC', '0', 'I', '100', 'Y', 'Y', 0, 100, '3', 'If this is greater than 0 (maximum of 100), then the budget protection garment loss option has a new field showing that is the percentage saving of the loss price if this insurance is in place.  This percentage is the default suggestion / fixed in the contract dialog and customer if the customer is not linked to a contract.  '|| chr(10) ||'It is taken into consideration in US Direct invoicing, loss charge monitor and route assistant bill for loss now', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHANGEDELIVERYWEEK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1 and change the route, it is also possible to change the delivery week (delivery scheme).', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGEDECREASEOFCIRCINV', 'N', 'B', 'N', 'Y', 'N', null, null, 'YN', 'This controls the default value for the Customer Ordering tab field check box for Charging Decrease of circulating inventory.'|| chr(10) ||'Y = check box defaults to Y on ADD new customer'|| chr(10) ||'N = check box defaults to N on ADD new customer'|| chr(10) ||''|| chr(10) ||'NOTE: Only for periodical invoicing', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGEINCREASEOFCIRCINV', 'N', 'B', 'N', 'Y', 'N', 0, 1, 'YN', 'This controls the default value for the Customer Ordering tab field check box for Charging Increase of circulating inventory.'|| chr(10) ||'Y = check box defaults to Y on ADD new customer'|| chr(10) ||'N = check box defaults to N on ADD new customer'|| chr(10) ||''|| chr(10) ||'NOTE: Only for periodical invoicing', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGELOSSCHARGE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for this field in the garments tab in the customer form. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGELOSSCHARGENONGRM', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Ordering tab: Defines default value for Charge Loss Charge for Non-Garments'|| chr(10) ||''|| chr(10) ||'Also applies to contract dialog, product settings, non garment charges', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGELOSSFORPOOLITEMS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Default value for the checkbox charge loss for pool'|| chr(10) ||'0 = Do not charge loss for unique pool'|| chr(10) ||'1 = Charge loss for unique pool'|| chr(10) ||'Only used in module LOSSFORPOOL.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGELOSSUNIQUEPOOLDAYS', '90', 'I', '90', 'Y', 'N', 0, 999, '', 'Number of days for calculating the cut off date for pool. '|| chr(10) ||'Only relevant when setting LOSSFORPOOLMETHOD=2 (number of days)'|| chr(10) ||'Only used in module LOSSFORPOOL.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGERENTFORLOSS', 'Y', 'B', 'Y', 'Y', 'N', 0, 1, '1', 'This controls the charge rent for loss setting at customer and contract settings'|| chr(10) ||''|| chr(10) ||'NOTE: only applicable for US Direct invoicing, SettlementActive = Y and setting RENTALCHARGEFORLOSTGRMT = Y', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGEREPAIRS', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for this field in the garments tab in the customer form. ', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGERESIDUALVALUE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for this field in the garments tab in the customer form. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGERESIDUALVALUENONGRM', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Ordering tab: Defines default value for Charging Residual Value for Non Garments'|| chr(10) ||''|| chr(10) ||'also applies to Contract Dialog, Product Settings, Non garment charges', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CHARGEWASHFIRSTISSUE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for checkbox  "Charge washes at  first issue".', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CLUSTEROBLIGATED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Billing TAB: Depending on this setting definition of a cluster is obligated or not. (only in EU billing TAB)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'COCDEFINITION', '1', 'I', '1', 'N', 'N', 1, 2, '', 'This setting defines the maximum length of the COC# / P-Site input-fields in the Customer dialog. Allowed lengths are 10 and 20 digits.'|| chr(10) ||'1 - Both input fields have a length of 10 digits'|| chr(10) ||'2 - Both input fields have a length of 20 digits '|| chr(10) ||'By default, the maximum length will be set to 10 digits.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CODEGARMENTSUNIQUELY', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Garments-tab: Default value for this field in the garments-tab in the Customer form. Which on it''s it is a default'|| chr(10) ||'for the field in productlist per customer, when a product of type of merchandise ''garments'' is added.'|| chr(10) ||'If set to Yes the system doesn''t allow to issue non-uniquely coded items.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'COGALLOWEDONLYPLPC', 'Y', 'B', 'Y', 'Y', 'N', null, null, 'Y;N', 'Module EXTENDEDCODEUNIQUECOG: default value for attribute in customer screen.'|| chr(10) ||'Yes: only allow to select products defined in PLPC to select for adding COG item.'|| chr(10) ||'No: allow to select other products (defined in COG wash price table) to select when adding COG item. The product will be added in the PLPC.'|| chr(10) ||'From 80305 version this setting is replaced by EXTENDEDCODEUNIQUECOGEXT', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'COGALLOWEDONLYPLPCEXT', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Module EXTENDEDCODEUNIQUECOG: default value for attribute in customer screen.'|| chr(10) ||'1: only allow to select products defined in PLPC to select for adding COG item.'|| chr(10) ||'2: allow to select other products (defined in COG wash price table) to select when adding COG item. The product will be added in the PLPC.'|| chr(10) ||'3: only allow to select restricted products defined in PLPC to select for adding COG item.'|| chr(10) ||''|| chr(10) ||'This setting is derived from the setting COGALLOWEDONLYPLPC but extended with a third option and it replaces it as of now.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'COGPRICETABLECODE', '-', 'S', '', 'N', 'N', null, null, '', 'Code of washprice table used for adding COG product code.'|| chr(10) ||'Used for optional module EXTENDEDCODEUNIQUECOG', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CONSIGNMENTNOTE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Delivery-tab: Default value for the field ''Consigment Note'' in the Customer form.'|| chr(10) ||'Recommended use: in US: No (because instead a direct invoice is printed).'|| chr(10) ||'In EU: Yes, for customers that get multiple containers.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CONSIGNMENTNOTELAYOUT', '1', 'S', '1', 'Y', 'N', null, null, '', 'Delivery-tab: Default value for the the field Consignmentnote Layout in the Customer form.', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'CONSIGNMENTNOTELEVEL', '0', 'I', '0', 'Y', 'Y', 0, 4, '', 'Possible values:'|| chr(10) ||'0 = No Consignment note'|| chr(10) ||'1 = Consignment Note on Customer level'|| chr(10) ||'2 = Consignment Note on Department level'|| chr(10) ||'3 = Consignment Note on Delivery Point level'|| chr(10) ||'4 = Consignment Note on Customer Reference level'|| chr(10) ||''|| chr(10) ||'Option 4 is only available when the PACKINGNOTEBYREFERENCE module is in the license or when system setting CONSIGNMENTDVREFERENCE is set to 1', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CONTRACTPOCLOSEACTION', '0', 'I', '0', 'Y', 'N', 0, 2, '1', 'This defines the default close action for the contract purchase order number screen in add mode.  And in fixed or default (so enable / disable) is used in modify mode'|| chr(10) ||'0 = Close when the value is reached or expiry date, '|| chr(10) ||'Note if the purchase order has a value of 0, then the default will be 1 (Close on expiry date) as, when the value is 0, close when value is reached is not a valid selection'|| chr(10) ||'1 = Close on expiry date (no value check)'|| chr(10) ||'2 = Close when value exceeds max percentage or expiry date', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CONTRACTUSAGE', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Single customer contract info'|| chr(10) ||'1 = Predefined contract'|| chr(10) ||'This setting is only applicable for module Master account management.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CORRECTOVERDELIVERIES', 'Y', 'B', 'N', 'Y', 'N', null, null, '', 'Delivery-tab: Defines the default value for  Correct overdeliveries-field in customer screen. If Yes then overdeliveries will be corrected by the next delivery.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CORRECTSHORTAGES', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Delivery-tab: Defines the default value for  Correct shortages-field in customer screen. If Yes the shortages will be corrected by the next delivery.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CREDITLIMIT', '0', 'F', '0', 'Y', 'N', 0, 999999, '', 'Billing-tab: Default value for credit squeeze percentage of the bill-to customer.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CREDITSQUEEZETYPE', '1', 'I', '1', 'Y', 'N', 1, 2, '', '1=Surcharge'|| chr(10) ||'2=Discount', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CUSTOMERASSOCIATION', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Default value for master account assiociation:'|| chr(10) ||'0 = Not applicable'|| chr(10) ||'1 = Association'|| chr(10) ||'(for master account)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CUSTOMERNAMELENGTH', '40', 'I', '40', 'N', 'N', 1, 40, '', 'Length of name that can be defined for customer.'|| chr(10) ||'Only used for specific import / exports.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CUSTOMERNREDITABLE', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'This setting indicates whether it is allowed to change the customer number or not. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'CUSTOMERREMARKLENGTH', '80', 'I', '80', 'N', 'N', 0, 1000, '', 'Length of remark that can be defined for customer.'|| chr(10) ||''|| chr(10) ||'It will not be possible to change the length to a value smaller than the current value to avoid loss of data.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DAYSNOPREPCHARGE', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'Garments-tab: Default value for this field in the garments tab of the customer screen. '|| chr(10) ||'Defines the number of days from the customer start date that no prep costs are charged.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DAYSPRIORTODELTOGENPACN', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Y means that the maximum number days prior to delivery date that the packing note can be generated entry field is shown in CPL and taken into account during packing note generation'|| chr(10) ||'N means no change in behaviour', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEBTORCHANGE', '2', 'I', '2', 'N', 'N', 0, 2, '', '0 = No check on not exported invoices when changing the debtor'|| chr(10) ||'1 = Show warning'|| chr(10) ||'2 = Show error message'|| chr(10) ||''|| chr(10) ||'NOTE: this is actually not exported ARTransactions', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEBTORCHANGEWITHOPENAR', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This controls the warning / stop / automatic action taken if a single Del to - Bill to customer has some open AR Transactions  and its bill to is changed.'|| chr(10) ||''|| chr(10) ||'0 = Warning "This del to customer has open AR Transactions and they will not be moved to the new Bill To customer" option of OK.'|| chr(10) ||''|| chr(10) ||'1 = Warning with option to move - so "This del to customer has open AR Transactions , do you want to automatically move them to the new bill to?  If you want to move them to a different account, please cancel and move them before changing the bill to".  Options of OK and cancel.'|| chr(10) ||''|| chr(10) ||'If the user does not have access to the customer financials screen in modify mode (so they don''t have permissions to use the Transfer Bill To feature) then this is a hard stop using the message in option 2 as another user will need to do the move.'|| chr(10) ||''|| chr(10) ||'2 = Hard stop "This del to customer has open AR Transactions, please move them before changing the bill to customer" option of cancel.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTBULKDELIVERY', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Delivery-tab: Default value for the field ''Bulk Delivery'' in the Customer form.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTCUSTOMERMAX', '99999999', 'L', '99999999', 'N', 'N', 0, 999999999999, '', 'This setting indicates the upper boundary of the range from which the first free number should be picked.'|| chr(10) ||'It will be used in combination with the system settings DEFAULTCUSTOMERNR and DEFAULTCUSTOMERMIN.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTCUSTOMERMIN', '1', 'L', '1', 'N', 'N', 0, 999999999999, '', 'This setting indicates the lower boundary of the range from which the first free number should be picked.'|| chr(10) ||'It will be used in combination with the system settings DEFAULTCUSTOMERNR and DEFAULTCUSTOMERMAX.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTCUSTOMERNR', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Defines how a new customer number is generated.'|| chr(10) ||''|| chr(10) ||'0=No default'|| chr(10) ||'1=Display as default the first free number'|| chr(10) ||'2=Display as default the highest existing number plus 1'|| chr(10) ||'3=Display as default the first free number within the indicated range'|| chr(10) ||'4=Display as default the first free number within the indicated range. The customernumber can be changed but must remain within this range.'|| chr(10) ||''|| chr(10) ||'Options 3 and 4 will be used in combination with the system settings DEFAULTCUSTOMERNRMIN and DEFAULTCUSTOMERMAX.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTEFFICIENCYVALUE1', '0', 'I', '0', 'Y', 'N', 0, 100, '', 'Only used in Efficiency check module. Default value for first check.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTEFFICIENCYVALUE2', '0', 'I', '0', 'Y', 'N', 0, 100, '', 'Only used for Efficiency check module. Default for second efficiency check.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTEFFICIENCYVALUE3', '0', 'I', '0', 'Y', 'N', 0, 9999, '', 'Only used for Efficiency Check module. Default value for third efficiency check.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTEMAILDIRECTINVOICE', '2', 'I', '2', 'Y', 'N', 1, 3, '1', 'Defines default value for Customer Billing attribute: Email Direct Invoice To:'|| chr(10) ||'1 = Del To Invoice Contact'|| chr(10) ||'2 = Bill To Invoice Contact'|| chr(10) ||'3 = Del To and Bill To Invoice Contacts', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTMLPPERCENTAGE', '0', 'F', '0', 'Y', 'N', 0, 100, '', 'Default percentage for MLP (Material Loss Protection). Only used if both modules BUDGETPROTECTION and BUDGETPROTECTIONMLP are active.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTMMPPERCENTAGE', '0', 'F', '0', 'Y', 'N', 0, 100, '', 'When Budget Protection is used, then this setting can be used to define a default MMP (Material Maintenance Protection) percentage that will be used when creating a contract, customer or product that is eligible for MMP.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when Budget Protection is in the license', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTPAYMENTTYPE', '1', 'I', '1', 'Y', 'Y', 1, 7, '', 'This is a default value that defaults the payment type of a new customer. Possible values:'|| chr(10) ||'1=Check'|| chr(10) ||'2=Credit Card'|| chr(10) ||'3=EFT'|| chr(10) ||'4=EDI'|| chr(10) ||'5=Accept Giro'|| chr(10) ||'6=Automatic Collection '|| chr(10) ||'7=Via Pay-by Customer', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTREDUCEFACTOR', '0', 'I', '0', 'Y', 'N', 0, 6, '', 'Only used for the module LINENSMOOTHENER.'|| chr(10) ||'0 = Not applicable (Linen delivery smoothener not used)'|| chr(10) ||'1 = Reduce factor A'|| chr(10) ||'2 = Reduce factor B'|| chr(10) ||'3 = Reduce factor C'|| chr(10) ||'4 = No reduce allowed'|| chr(10) ||'5 = Allow use of reduction (no factor used)'|| chr(10) ||'6 = Reduce not allowed (factor not used)'|| chr(10) ||'	', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTREPLACEMENTGRADE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls which quality grade should be selected by default as the minimum grade to be used in case of replacement (or additional issue) when adding a new customer. Possible values:'|| chr(10) ||'0 - Use the grade setup as the default grade.'|| chr(10) ||'1 - Use the highest possible grade of category New.'|| chr(10) ||'2 - Use the highest possible grade of category Used.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFAULTUSEPRODSIZESURCH', '1', 'I', '1', 'Y', 'N', 1, 2, '1', 'Default value for contract and customer for attribute "use product size surcharge pricing" for CHARGESPECIALSIZE module'|| chr(10) ||'Default = 1 = Yes'|| chr(10) ||'2 = No', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFCONFIRMDEPTCHANGESCAN', '1', 'I', '1', 'Y', 'N', 1, 4, '', 'Via this setting a default value can be set for a flag at customer level to indicate whether a department change at Inscan or Outscan should be confirmed or not. Possible values:'|| chr(10) ||'1 - The configuration is done on plant level via the existing system setting INSCANCONFIRMDEPTCHANGE and OUTSCANCONFIRMDEPTCHANGE. This is also the factory default.'|| chr(10) ||'2 - On customer level the default value will be yes but can be modified by the user.'|| chr(10) ||'3 - On customer level the default value will be no but this can be modified by the user.'|| chr(10) ||'4 - Separate setting on customer level for inscan and outscan. For outscan in addition a confirm message can be set on consumption point. Option 4 will be available from 9.04.01.'|| chr(10) ||''|| chr(10) ||'The setting will only have an effect when the message for customer change has been activated. It is not logical to show a message when the department changes but not when  the customer changes.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFCUSTOMERONSITEDELSCAN', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'The setting controls if the Onsite Delivery Scan checkbox will be checked or unchecked by default when adding a new customer. Possible values:'|| chr(10) ||'No - The checkbox will be unchecked by default'|| chr(10) ||'Yes - The checkbox will be checked by default'|| chr(10) ||''|| chr(10) ||'When defined as a fixed default, then the checkbox will be disabled and cannot be overruled by the user.'|| chr(10) ||''|| chr(10) ||'The setting is only relevant when the ROUTEASSISTANTDELIVERYSCAN module is in the license', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEFPARTIALINVDELSALESNOTE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether the checkbox Allow partial invoicing of sales / sales delivery notes on the Billing tab of the Customer dialog will be checked by default or not. When defined as a fixed setting, the checkbox will be disabled and the user will not be able to overrule it.'|| chr(10) ||'Possibe values:'|| chr(10) ||'0 - Set the checkbox by default to unchecked'|| chr(10) ||'1 - Set the checkbox by default to checked'|| chr(10) ||'Default value 0'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the TRADE module is in the license. Without this module, the checkbox is not visible to the user.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DELINQUENTAFTER', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'US Billing-tab: Value for the number of days after which the billing to customer is declared as delinquent for not paying the invoiced amounts.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DELIVERYDAYS_US', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Delivery-tab: Defines if customer delivery days are defined in the US way or, if set to No in the EU way.'|| chr(10) ||'In the US way the delivery days are indicated with a D (delivery) or B (delivery and bill).'|| chr(10) ||'In the EU way only a checkbox is used to indicate delivery yes or no.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DELIVERYNOTELAYOUT', '1', 'S', '1', 'Y', 'N', null, null, '', 'Delivery-tab: Defines the default layout for the delivery note. This default is used in the Customer Form.', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'DEPARTMENTRENTORSALES', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether the items for a wearer belonging to a department will either always be sold, rented or both. The selected option will be used as a filter for the allowed reason codes when generating work orders for personalized garments for these wearers. By default this functionality will never be avialble. Possible values:'|| chr(10) ||'0 = Not applicable '|| chr(10) ||'1 = Both rented garments and sales items are allowed'|| chr(10) ||'2 = Only rented garments are allowed'|| chr(10) ||'3 = Only sales items are allowed'|| chr(10) ||'Default value 0.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DEPRECIATIONLOSSCHARGE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'When set to Yes, it is allowed to use depreciation on loss charge, A residual value scheme for loss charge depreciation must be specified on the PLPC.'|| chr(10) ||'Note: this only concerns loss charges for unreturned personalized garments for direct invoicing. '|| chr(10) ||'It has no relation with loss charges for uniquely coded pool items.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'DISPLAYSTREET2', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This setting indicates whether the second address line ADDRESS.Street2 should be displayed on both the Customer General and Customer Delivery tab page, in cost center and in cost center group', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'EFFICIENCYCHECKCONTACT', '-', 'S', '-', 'N', 'N', null, null, '', 'Only used for module CustomerEfficiencyCheck. This setting specifies the contact category for the contact that is created in the efficiency check process.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ERPCUSTOMERINTEGRATION', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting controls whether it is allowed to manually add or delete a customer, customer cost center, customer delivery point, customer department or consumption point or change their logical keys like customer number, cost center code, delivery point code, department number or consumption point number. Possible values:'|| chr(10) ||'0 = It is not allowed to create/delete these objects manually, they will be imported from a thid-party ERP application, since that external application is leading with respect to the customer structures.'|| chr(10) ||'1 = It is allowed to create/delete these objects manually, or change their logical key values.'|| chr(10) ||'2 = Same as 1, and in addition to that, it is also allowed to change some other values for these objects.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module ERPINTEGRATION is active.'|| chr(10) ||'Option 2 is only considered as of release 9.08.00.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'FINANCECHARGEDAYS', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'US Billing-tab: Used as default value for the number of days after which the financial charges are applied.'|| chr(10) ||'0 means no financial charges ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'FINANCECHARGEPUTON', '1', 'I', '1', 'Y', 'N', 1, 2, '', 'US Billing-tab: Used as default value. It defines where the finance charges will be put on.'|| chr(10) ||'1 = Invoice'|| chr(10) ||'2 = Statement', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'FLATRATEDTYPECHARGE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for checkbox called "One time charge for new employment"  in the garment charges tab in the prep charge section of the screen.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'GALAXIELOSSFORPOOLWEBSERV', '0', 'I', '0', 'Y', 'Y', 0, 1, '', 'Default state of Customer.Include customer in Loss for Pool Webservice'|| chr(10) ||'Only relevant if the module GALAXIE is in the license'|| chr(10) ||''|| chr(10) ||'Value 0 – No (default)'|| chr(10) ||'Value 1 – Yes, invoice via Galaxie', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'GARMENTEXCHANGECHARGE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'controls the default value for Garment Charge Exchange Charge on the contract and customer dialog'|| chr(10) ||'0 = Charge Exchange Charge charge defaults to No'|| chr(10) ||'1 = Charge Exchange Charge charge defaults to Yes', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'GARMENTEXCHANGECHRGEPRICE', '0', 'F', '0', 'Y', 'N', 0, 99, '', 'The default value used for the exchange charge (price) in the contract and the customer dialog.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'GARMENTRENTSPECIFICATION', '1', 'I', '1', 'Y', 'N', 1, 8, '', 'Garments-tab: Default value for customer field garmentrentspecification .Can have the following values :'|| chr(10) ||'1=Products per Wearer'|| chr(10) ||'2=Products per Wearer Cond.'|| chr(10) ||'3=Wearer totals only'|| chr(10) ||'4=Quantities per Product'|| chr(10) ||'5=Number of wearers per total price'|| chr(10) ||'6=Wearer function'|| chr(10) ||'7=Wearer function special price'|| chr(10) ||'8=Products per wearer excl.COG', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'GARMENTRESVALUESCHEME', '0', 'S', '0', 'Y', 'N', null, null, '', 'Will be obsolete soon.'|| chr(10) ||'Garments-tab: Default value for this field in the garments tab of the customer screen. '|| chr(10) ||'Value must exist as code in the residual value schemes table.', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'GENERALPREPCHARGEDEFAULT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'With this setting the checkbox ''General prep charges'' in the Garment Charges tab is set by default.'|| chr(10) ||'No = not checked'|| chr(10) ||'Yes = checked.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INACTIVATECUSTOMER', '0', 'I', '0', 'N', 'N', 0, 2, '', 'Inactivate customer from the Customer screen:'|| chr(10) ||'0 = Fill date inactive only. No additional processing.'|| chr(10) ||'1 = When date inactive is filled, the record lost business process is started. Using this process is obligated.'|| chr(10) ||'2 = When date inactive is filled, the record lost business process is started. Usage is not obligated, additional button is available to set the date inactive only.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INSCANBASEDFORECAST', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for inscan based forecast. Used in sortingsystem module.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INSURANCEDEFAULTS', '0', 'I', '0', 'Y', 'N', 0, 7, '', 'Relevant for module EasyCare'|| chr(10) ||'0= Not charged / not applicable       :  no default insurance settings'|| chr(10) ||'1= For Repairs		     : new customers are by default set for insurance for Repairs		2= For Loss charges		     : new customers are by default set for insurance for  Loss'|| chr(10) ||'3= For Repairs and Loss charges '|| chr(10) ||'4= For Residual Value'|| chr(10) ||'5= For Repair and Residual Value'|| chr(10) ||'6= For Residual Value and Loss Charge'|| chr(10) ||'	7= For Repair Loss Charge and Residual Value', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INVNOCHARPERLINE', '50', 'I', '50', 'N', 'N', 1, 100, '', 'US Billing-tab: Number of characters on one line for customer invoice comment. Value depends on invoice layout (what will fit in the space intended for comments).', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INVNOOFLINESPERCOMMENT', '6', 'I', '6', 'N', 'N', 1, 20, '', 'US Billing-tab: Number of lines per customer invoice comment. Value depends on invoice layout (what will fit in the space intended for comments)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INVOICEMETHOD', '0', 'I', '0', 'Y', 'Y', 0, 2, '', 'Possible values:'|| chr(10) ||'0 (in arrear)'|| chr(10) ||'1 (in advance, correct additions only)'|| chr(10) ||'2 (in advance, correct both additions and deletions)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'INVOICESPECIALSCANS', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Customer Residential Settings - the checkbox Invoice Special Scans is default unselected'|| chr(10) ||'1 = Customer Residential Settings - the checkbox Invoice Special Scans is default selected', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'LABELLAYOUTPRICE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Single label layout price'|| chr(10) ||'1 = Separate Laundry Owned and Customer Owned Label Price'|| chr(10) ||'2 = Allow to specify a specific price for a label layout, and general customer owned and laundry owned label price'|| chr(10) ||'Option 1 and 2 only work for periodical invoicing.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'LINENDELIVERYSTABILIZER', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting is only used for module LINENDELIVERYSTABILIZER.'|| chr(10) ||'0 = Standard'|| chr(10) ||'1 = Linen Delivery Stabilizer'|| chr(10) ||'The Linen delivery stabilizer is a different formula to calculate the delivery based on soil count. The purpose of this formula is to reduce the deviation.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'LOCKERMANAGEMENTDEFAULT', '0', 'I', '0', 'Y', 'N', 0, 1, '1', 'Controls the default / fixed values for fields "Locker Management" and "Obligated Use of Bank / Locker for Every Wearer" on the customer dialog, garments tab.'|| chr(10) ||''|| chr(10) ||'0 = both fields default to N but may be overridden by some other settings'|| chr(10) ||'1 = both fields default to Y', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'LOSSFORPOOLTRIGGER', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Default value for the field charge loss for pool not scanned since, at the billing tab'|| chr(10) ||'This setting determines how the cut off date for the loss calculation is determined.'|| chr(10) ||'0 = Cut off date is based on outscan date'|| chr(10) ||'1 = Cut off date is based on last scan date (can be any scan, for example on-site inventory scan)'|| chr(10) ||'2 = Cut off date is based on delivery date'|| chr(10) ||'See also setting LOSSFORPOOLMETHOD in Billing Settings group'|| chr(10) ||'Only used in the module LOSSFORPOOL. Option 2 is only available as of v9.02.00', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'MINIMUMINVOICEAMOUNT', '0', 'F', '0', 'Y', 'N', 0, 999999, '', 'US Billing-tab: default value for  the minimum invoice amount.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'MINRENTMAXWEEKS', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'This setting is used as a default value for the Minimum Rent Weeks when defining a new customer. When defined as a fixed setting the value of the setting will be copied to the new customer and cannot be changed from the user. When defined as a default value, it will also be copied to the new customer, but it can still be changed from the user.'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module RENTBASEDONRETURNWEEKS is in the license and can only be used in combination with EU invoicing. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'MOVESTOPMOVEUP', '0', 'I', '0', 'N', 'N', 0, 1, '', 'When set to 1 in case a stop is moved then automatically the stop with the same number and all higher stop numbers are moved up.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'MULTIPLEINVANDSTMCONTACTS', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This controls if you are allowed to have multiple contacts set as invoice or statement contacts.'|| chr(10) ||''|| chr(10) ||'0 = default = No'|| chr(10) ||'1 = yes'|| chr(10) ||''|| chr(10) ||'NOTE: Manual sending of invoices will support this but manual emailing of statements will not'|| chr(10) ||'For versions less than 9.10. the emailing scheduled processes for invoices and statements will be blocked', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'NOEMBLEMCHARGE1STINVOICE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Controls the default / fixed value for No Emblem charges on the first invoice in the contract and customer dialog'|| chr(10) ||''|| chr(10) ||'0 = No Emblem charges on the first invoice = No'|| chr(10) ||'1 = No Emblem charges on the first invoice = Yes', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'NOPREPCHARGE1STINVOICE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'Controls the default / fixed value for No Prep charges on the first invoice in the contract and customer dialog'|| chr(10) ||''|| chr(10) ||'0 = No Prep charges on the first invoice = No'|| chr(10) ||'1 = No Prep charges on the first invoice = Yes', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ONETIMECHARGE', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 = Not applicable / No one time charge per client'|| chr(10) ||'1 = One time charge for adding a new client. Charge is added on the first client delivery note for a new client.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'OPTIMIZEDLOADPACKINGDOC', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether a dedicated packing document, other than a regular packing note should be printed when generating packing notes for a customer in case Optimzed Load Packing is enabled for this customer. The system setting will be used as a defaullt for the value at customer level. Possible values:'|| chr(10) ||'0 = Print the regular packing note (default)'|| chr(10) ||'1 = Print the dedicated optimized load packing document instead of the regular packing note'|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the LOADOPTIMIZER module is active. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'OTHERBUBILLTO', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y it is possible to select a bill to customer that belongs to another business unit then the deliver to customer.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PAYMENTTABWITHEXTERNALAR', 'NNNN', 'S', 'NNNN', 'N', 'N', 4, 4, 'HRN', 'This setting is used in the US when the AR is outside of ABSSolute - so only relevant when system setting BILLINGTAB = 2 (US)'|| chr(10) ||''|| chr(10) ||'If set to anything apart from NNNN, then all fields on the Contract and Customer US Payments tab are hidden apart from the Payment Terms and Finance charge and these are controlled by the settings below.'|| chr(10) ||''|| chr(10) ||'The system setting value is a string of 4 characters were'|| chr(10) ||'   H = hide'|| chr(10) ||'   R = read only'|| chr(10) ||'   N = Not controlled by this setting (other settings such a contract compliancy may still affect this field)'|| chr(10) ||''|| chr(10) ||'1st value - Contract Payment terms'|| chr(10) ||'2nd value - Contract Finance charges'|| chr(10) ||'3rd value - Customer Payment terms'|| chr(10) ||'4th value - Customer Finance charges'|| chr(10) ||''|| chr(10) ||'So HNRN'|| chr(10) ||'Contract dialog with only the finance charge fields visible and not controlled by this setting (payment terms hidden)'|| chr(10) ||'Customer dialog with only the payment term visible but disabled (read only) and the finance charge fields visible and not controlled by this setting'|| chr(10) ||'All other fields would be hidden', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PHONEFAXLENGTH', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Length of phone/fax number is 15'|| chr(10) ||'1 = Length of phone/fax number is 30', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'POSTALCODELOOKUP', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This  setting indicates whether the city should be filled in automatically after entering the postal code. This setting is only active when the module POSTALCODE is in the license of the plant', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PREPANDEMBCHARGEON1STINV', '0', 'I', '0', 'N', 'N', 0, 2, '1', 'This defines if the no prep and or no emblem charge on the first invoice settings on contract or customer screens refers to the first generated invoice for the customer or the first generated invoice for the wearer.'|| chr(10) ||''|| chr(10) ||'0 = default = no prep or emblem charge means no charge on the first generated invoice for the customer'|| chr(10) ||'1 = no prep or emblem charge means no charge on the first generated invoice for the wearer'|| chr(10) ||'2 = no prep or emblem charge means no charge on the first generated invoice for the wearer if the wearer was keyed in (created) before the customer was installed (Customer.FirstServiceDate)'|| chr(10) ||''|| chr(10) ||'NOTE: Only available for US Direct invoicing'|| chr(10) ||'NOTE: the decision for free of charge when at wearer level (1 & 2) is done when the garments are issued.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PREPEMBLEMSPECIFICATION', '3', 'I', '3', 'Y', 'Y', 1, 4, '', 'Used in combination with Garment Rent Specification to determine the way the prep and emblem charges are printed on the direct invoice.'|| chr(10) ||''|| chr(10) ||'1 - Per Wearer Detailed'|| chr(10) ||'2 - Per Wearer Summarized'|| chr(10) ||'3 - Detailed'|| chr(10) ||'4 - Summarized', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PREWASHFORGARMENTS', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting will be used to control whether the new checkbox "Pre-Wash for Garments" should be set to checked or not checked by default when adding a new customer. The user may only change this value when defined as a default value. When set as a fixed value, then the user cannot change this default value at all. Possible values:'|| chr(10) ||'0 = checkbox is not set to checked (default)'|| chr(10) ||'1 = checkbox is set to checked', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'PRINTTAXONAPPENDIX', 'N', 'B', 'N', 'Y', 'Y', null, null, '', 'Define if Tax should be printed on invoice appendices.'|| chr(10) ||'Please note: this setting is applicable for only a few invoice appendices, not all. If the customer does not have invoice appendices defined then it is not applicable at all.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION1', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 1 can be chosen.'|| chr(10) ||'1=Products per Wearer'|| chr(10) ||'Product Name			Invent.     Charge Price'|| chr(10) ||'SSSH	BILL ANDERSON	11	5	3'|| chr(10) ||'PANT	BILL ANDERSON	11	5	4'|| chr(10) ||'JCKT	BILL ANDERSON	2	1	4'|| chr(10) ||'SSSH	RICHARD BROWN	11	5	3'|| chr(10) ||'PANT	RICHARD BROWN	11	5	4', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION2', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 2 can be chosen.'|| chr(10) ||'2=Products per Wearer Condensed'|| chr(10) ||'Pant Shirt  Item Name			Invent	Charge	Price'|| chr(10) ||'5       5	 P and S  BILL ANDERSON			7'|| chr(10) ||'1	 JCK  BILL ANDERSON			4'|| chr(10) ||'5      5	 P and S  JOE WILLIAMS		 	7.5', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION3', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 3 can be chosen.'|| chr(10) ||'3=Wearer totals only'|| chr(10) ||'Name		Inventory	Charge	Price'|| chr(10) ||'BILL ANDERSON			11'|| chr(10) ||'RICHARD BROWN			7'|| chr(10) ||'JOE WILLIAMS			7.5', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION4', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 4 can be chosen.'|| chr(10) ||'4=Quantities per Product'|| chr(10) ||'Product Name		    Invent	Charge	Price'|| chr(10) ||'140005 Pant Navy 		     33		12'|| chr(10) ||'150023 Short Sleeve Shirt White 22		6'|| chr(10) ||'210099 Jacket Green	      2		4', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION5', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 5 can be chosen.'|| chr(10) ||'5=Number of wearers per total price'|| chr(10) ||'Product Name			Inventory	Charge	Price'|| chr(10) ||'           1 Wearer   at $  7.00			1	  7'|| chr(10) ||'           2 Wearers at $  7.50			2	  7.5'|| chr(10) ||'           1 Wearer   at $11.00			1	11', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION6', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 6 can be chosen.'|| chr(10) ||'6=Number of wearers per function   (Description=function description, Quantity=#employments)'|| chr(10) ||'Description		Quantity  Price   Amount'|| chr(10) ||'Service Engineer                           3       9.50     28.50'|| chr(10) ||'Welder                                           7       7.00     49.00', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RENTSPECIFICATION7', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Garments-tab: Defines if for the field garment rent specification if specification 7 can be chosen.'|| chr(10) ||'7=Number of wearers per function Special Price'|| chr(10) ||'Note: only used in periodical invoicing', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'REPAIRCHARGES', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Garments-tab: Default value for this field in the garments tab in the customer form. '|| chr(10) ||'0= Repairs are not charged.'|| chr(10) ||'1= Repairs are charged and shown condensed (one line) on the invoice'|| chr(10) ||'2= Repairs are charged and shown detailed (per repairtype) on the invoice.', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'REPAIRCOG', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Garments-tab: Default value for this field (repair charges customer owned) in the garments tab in the customer form. '|| chr(10) ||'0= Not Allowed'|| chr(10) ||'1= Allow, don''t charge'|| chr(10) ||'2= Allow and Charge', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'REPAIRRENTED', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Garments-tab: Default value for this field (repair charges laundry owned) in the garments tab in the customer form. '|| chr(10) ||'0= Not Allowed'|| chr(10) ||'1= Allow, don''t charge'|| chr(10) ||'2= Allow and Charge', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'REPAIRSPECIFONINVOICE', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0 = Sumarized for LOG / COG'|| chr(10) ||'1 = Summarized per repair type'|| chr(10) ||'2 = Detailed per Wearer', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'REPLACEMENTGRADE', 'N', 'S', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for the Quality grade that has to be entered in the garments tab of the customer screen under minimum grade ''afterwards''.'|| chr(10) ||'This value must exist as code in quality grades table.', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'RESTOCKFEEDEFAULT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'With this system setting the checkbox ''restocking fee'' in the Garment Charges tab is set by default.'|| chr(10) ||'No = not checked'|| chr(10) ||'Yes = checked', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RETURNGARMENTS', '2', 'I', '2', 'Y', 'N', 1, 7, '', 'Garments-tab: default value for this field in the garments tab of the customer form. '|| chr(10) ||'Possible values'|| chr(10) ||'1=Next visit'|| chr(10) ||'2=Next week same route'|| chr(10) ||'3=10 day delay basis'|| chr(10) ||'4=return route in route schedule.'|| chr(10) ||'5=14 day delay basis'|| chr(10) ||'6=28 day delay basis'|| chr(10) ||'7=according to delivery scheme'|| chr(10) ||'Typicall use: 2.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RETURNLINEN', '1', 'I', '1', 'Y', 'N', 1, 7, '', 'Delivery-tab: System setting for Customer form'|| chr(10) ||'Can have following values :'|| chr(10) ||'1=next visit'|| chr(10) ||'2=next week,same route'|| chr(10) ||'3=10 days delay basis'|| chr(10) ||'4=return route in route schedule'|| chr(10) ||'5=14 day delay basis'|| chr(10) ||'6 =28 day delay basis'|| chr(10) ||'7=according to delivery scheme', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'RETURNRENTMAXWEEKS', '0', 'I', '0', 'Y', 'N', 0, 999, '', 'This setting is used as a default value for the Return Rent Weeks when defining a new customer. When defined as a fixed setting the value of the setting will be copied to the new customer and cannot be changed from the user. When defined as a default value, it will also be copied to the new customer, but it can still be changed from the user. '|| chr(10) ||''|| chr(10) ||'This setting is only relevant when the module RENTBASEDONRETURNWEEKS is in the license and can only be used in combination with EU invoicing.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'ROUTEOBLIGATED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Delivery-tab: Defines if the selection of a route in the delivery tab of the customer screen is obligated or not. If this setting is No it is still possible to use route functionality. Put this setting to Yes if the system should force the user to put a customer in a route.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SENDSTATEMENT', '2', 'I', '2', 'Y', 'N', 1, 3, '', 'US Billing-tab: Defaults the way a statement can be sent to a bill-to customer:'|| chr(10) ||'1 = Always with a certain frequency '|| chr(10) ||'2 = Only if invoices are past due'|| chr(10) ||'3 = Never', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SEPAAUTHORIZATION', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'Possible values:'|| chr(10) ||'0	Extra fields for SEPA Authorization not visible on customer payment tab'|| chr(10) ||'1	Extra fields for SEPA Authorization visible and enabled on customer payment tab for all '|| chr(10) ||'                      the payment types'|| chr(10) ||'2	Extra fields for SEPA Authorization only visible and enabled on customer payment tab for '|| chr(10) ||'                      those customers with payment type ''automatic collection'' .', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SEPARATEHOUSENR', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If set to Yes, the invoice address will be entered using separate fields for the housenumber and optional extension.'|| chr(10) ||'Must be used in combination with EXTERNALINVOICEPRINT module.'|| chr(10) ||'Mind: conversion script must be run manually when activated.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SHOWCRMCUSTOMERNO', '0', 'I', '0', 'Y', 'N', 0, 2, '0;1;2', 'Being able to connect the external CRM Customer Number in the customer in ABSSolute.'|| chr(10) ||''|| chr(10) ||'Possible Values:'|| chr(10) ||''|| chr(10) ||'0 = Not Visible'|| chr(10) ||'1 = Visible, not mandatory'|| chr(10) ||'2 = Visible, mandatory', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SHOWINTERNALADMINCUSTOMER', '0', 'B', '0', 'N', 'N', null, null, '1', 'Defines if the internal admin customer field is shown on the customer dialog'|| chr(10) ||''|| chr(10) ||'True = show'|| chr(10) ||'False (default) = don''t show', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SHOWONDELIVERYNOTE', '0', 'I', '0', 'Y', 'N', 0, 15, '', 'Garments-tab: default value for the field -Show Scans on Deliverynote- in the garments tab of the customer form. Possible values'|| chr(10) ||'0=Qty per Prod'|| chr(10) ||'1=Qty  per Prod/Size'|| chr(10) ||'2=Qty  per Prod + Outscan from Stock'|| chr(10) ||'3=Qty  per Prod/Size + Outscan from Stock'|| chr(10) ||'4=Qty per Prod + all Outscan'|| chr(10) ||'5=Qty  per Prod/Size + all Outscan'|| chr(10) ||'6= Qty  per Prod+ Outscan from Stock+ all Outscan'|| chr(10) ||'7= Qty  per Prod/Size + Outscan from Stock+ all Outscan'|| chr(10) ||'8=Qty  per Prod+ Ret to stock'|| chr(10) ||'9=Qty per Prod/Size + Ret to stock'|| chr(10) ||'10=Qty  per Prod + Ret to stock+ Outscan from Stock'|| chr(10) ||'11= Qty  per Prod/Size + Ret to stock+ Outscan from Stock'|| chr(10) ||'12= Qty  per Prod+ Ret to stock+ all Outscan'|| chr(10) ||'13= Qty  per Prod/Size + Ret to stock+ all Outscan'|| chr(10) ||'14= Qty  per Product + Ret to stock+ Outscan from Stock+ all Outscan'|| chr(10) ||'15 = Qty  per Prod/Size + Ret to stock+ Outscan from Stock+ all Outscan', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SHOWPHONEFAXMASK', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This setting indicates whether the predefined phone mask should be filled in automatically by default when adding a new record containing phone and/or fax numbers. This setting is only active when the module PHONEFAXVALIDATION is in the license of the plant. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SHOWREASONCODEOUTSCAN', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Define if the reason code description is displayed at outscan or not.'|| chr(10) ||'Y= show the reason code at outscan garments'|| chr(10) ||'N= hide the reason code at outscan garments (default value)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SIGNALINGWEEKS', '8', 'I', '8', 'Y', 'N', 0, 52, '', 'Contract Screen: Default value for field signaling weeks. It defines the number of weeks a signal is given to the user (via a report) that a contract is ending or that a manual anniversary price increase needs to be done.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SIGNATUREREQUIRED', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Default value for signature required (only applicable for PDA)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SIMPLEINVOICEPO', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This hides all contract purchase orders (invoice PO''s) and enables a basic free text customer level purchase order field.'|| chr(10) ||'If this is on, predefined and single customer contract level PO''s are hidden.'|| chr(10) ||''|| chr(10) ||'0 = Use contract level PO''s (default)'|| chr(10) ||'1 = Hide contract level PO''s and use basic customer level', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SOILCOUNT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Ordering-tab: Defines the default value for the field Soil Count in the Customer and Contract dialogs', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'STANDARDQTYDEFINITION', '1', 'I', '1', 'Y', 'N', 1, 2, '', 'Ordering-tab: Default for customer form it indicate how to interpret/define standard quantities.'|| chr(10) ||'1=delivery standards'|| chr(10) ||'2=usage standards', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'STATEMENTFREQUENCY', '100', 'I', '100', 'Y', 'N', 1, 445, '', 'US Billing-tab: A default value for the frequency with which a statement is sent to the bill to customer. See invoice frequencies screen for the possible values. ', 'Y');
execute CreateSystemSetting('Customer Screen Settings', 'STMTNOCHARPERLINE', '50', 'I', '50', 'N', 'N', 1, 100, '', 'US Billing-tab: Number of characters on one line for customer statement comment. Value depends on statement layout (what will fit in the space intended for comments)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'STMTNOOFLINESPERCOMMENT', '6', 'I', '6', 'N', 'N', 1, 20, '', 'US Billing-tab: Number of lines per customer statement comment. Value depends on statement layout (what will fit in the space intended for comments)', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SUPPRESSCOLDELNOTELINEN', '0', 'I', '0', 'Y', 'N', 0, 4, '', 'Via this setting a default value can be set  at customer level to indicate if columns NORM / VARIATION / ORDER / BALANCE will be displayed in delivery note for linen products. Possible values:'|| chr(10) ||'0=All columns are displayed for linen. Check box is not set at customer and not visible. (Default value)'|| chr(10) ||'1= On customer level the default value is no, but can be modified by the user.'|| chr(10) ||'2= On customer level the default value is no and cannot be modified by the user.'|| chr(10) ||'3= On customer level the default value is yes, but can be modified by the user.'|| chr(10) ||'4= On customer level the default value is yes, and cannot be modified by the user.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SUPPRESSPRINTDELNOTE', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Delivery-tab: default value for the field - Suppress Printing Of Delivery Notes - on the Delivery tab of the customer form. Possible values'|| chr(10) ||'N: Delivery notes will be printed automatically when generated'|| chr(10) ||'Y: No delivery notes will be printed when generated. They can only be printed when the user asks for a reprint manually.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SUPPRESSPRINTDELNOTEBATCH', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garment-tab: default value for the field - Suppress Printing Of Batch Delivery Notes - on the Garment tab of the customer form. Possible values'|| chr(10) ||'N: Delivery notes will be printed automatically when generated'|| chr(10) ||'Y: No delivery notes will be printed when generated. They can only be printed when the user asks for a reprint manually.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'SWINGSUITDELIVERY', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Garments-tab: Default value for this field in the garments tab of the customer form.'|| chr(10) ||'Swingsuit delivery is a delivery in two consecutive weeks: i.e. first week 6 second week 5.'|| chr(10) ||'Recommended use: In US mostly put to Y.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'USEBUNDLES', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Delivery-tab: Default value for the field Uses Bundles. Uses bundles determines if the ordered quantities for this customer are rounded to the standard bundle quantity. Rounded in this case means round up, so that the customer always gets enough. If the customer has multiple deparments the use bundles checkbox on department level is valid.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'USENATIONALPREFIX', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This setting indicates whether the national prefix should be added to the phone and/or fax number when entering it into the system. As a result of that, a predefined international phone number mask will be used otherwise a predefined national phone number mask will be applied. This setting is only active when the module PHONEFAXVALIDATION is in the license of the plant. ', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'USEPHONEFAXMASK', '0', 'I', '0', 'Y', 'N', 0, 2, '', 'This setting indicates whether a predefined mask should be applied to phone and/or fax numbers when entering them into the system. This setting is only active when module PHONEFAXVALIDATION is in the license of the plant. '|| chr(10) ||'0 = No. Do not use the functionality at all'|| chr(10) ||'1 = Flexible: A warning will be given to inform the user in case of an invalid format. It is still possible to save the record'|| chr(10) ||'2 = Restrictive: A warning will be given to inform the user in case of an invalid format. Only valid formatted phone/fax numbers are accepted. No possibility to save the record', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'USEWEARERGARMENTSBUDGET', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for using wearer budget in customer screen.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VATNUMBERAUTOFILL', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'This setting indicates whether the VAT number should be filled in automatically after entering the CoC Number. This setting is only active when the module BDE is in the license of the plant.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VATNUMBERLENGTH', '15', 'I', '15', 'N', 'N', 15, 30, '', 'This setting defined the length of the VAT number. Minimum length is 15, maximum length is 30. Please note that decreasing the value can cause problems since there can be customers which have a VAT number that can be longer than the new maximum length. So it is stronly encouraged not to decrease the length.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VATNUMBEROBLIGATED', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When this system setting is Y and checkbox ''Charge Vat'' is checked in customer dialog ,then entry of the vatnumber of the customer is obligated, else not.', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXADDCLEANINGCLIENTID', '-', 'S', '-', 'N', 'N', null, null, '', 'This defines the clientID used for the REST address cleaning web service call '|| chr(10) ||''|| chr(10) ||'Only used for module VERTEX and when system setting VERTEXADDRESSCLEANING is switched on', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXADDCLEANINGSECURITY', '-', 'S', '-', 'N', 'N', null, null, '', 'The trusted ID used for calling the vertex SOAP address cleaning web service'|| chr(10) ||''|| chr(10) ||'And the Client Secret for the replacement REST address cleaning web service', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXADDCLEANINGTOKENURL', '-', 'S', '-', 'N', 'N', null, null, '', 'This defines the URL used to get the security token for the REST address cleaning web service'|| chr(10) ||''|| chr(10) ||'Only used for module VERTEX and when system setting VERTEXADDRESSCLEANING is switched on', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXADDCLEANINGURL', '-', 'S', '-', 'N', 'N', null, null, '', 'The url used to connect to the Vertex SOAP address cleaning web service'|| chr(10) ||'And the url used to connect to the replacement REST address cleaning web service', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXADDRESSCLEANING', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'This defines if vertex address cleaning is in use.  This is only applicable for module VERTEX'|| chr(10) ||''|| chr(10) ||'0 = no (default)'|| chr(10) ||'1 = yes - so addresses must be cleaned via the vertex application and a valid tax area id is needed for contact, delivery and billing addresses before the customer can be saved'|| chr(10) ||''|| chr(10) ||'NOTE: This is also used for the REST replacement of the Vertex SOAP call', 'N');
execute CreateSystemSetting('Customer Screen Settings', 'VERTEXUPDATEADDRESS', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This defines if the address cleansing from the SOAP Vertex web service (for a confidence factor of 100) or replacement REST web service (regardless of confidence factor) is successful , and the returned address is not exactly the same as the stored address in ABSSolute, should the address be automatically updated'|| chr(10) ||''|| chr(10) ||'0 = no, address updating will be a manual choice'|| chr(10) ||'1 = yes, address updating for successful cleaning will be automatic'|| chr(10) ||'2 = yes, address and the tax area ID will be updated (REST version only)', 'N');
execute CreateSystemSetting('Product Screen Settings', 'ADDPRODUCTPERPLANT', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Used to determine whether products should be available for all plants and business units.'|| chr(10) ||'1 = add product as active to all plants (standard functionality)'|| chr(10) ||'2 = add product to all plants, set active for current plant only'|| chr(10) ||'3 = add product to all plants, ask for which plant(s) it should be set active. Only ask this question in case there are multiple plants.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'ALLOWDEACTIVATESIZE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Default N'|| chr(10) ||'When Y  show active Y/N on modify productsize and filter in PLPC for active sizes only when creating new records.'|| chr(10) ||''|| chr(10) ||'This is only honored in PLPC NEW record creation (not modify), no affect anywhere else in ABSSolute', 'N');
execute CreateSystemSetting('Product Screen Settings', 'ALLOWSUPPRESSONPACKINGRPT', '0', 'B', '0', 'N', 'N', null, null, '', 'Controls if the field "Suppress Printing on Packing Documents" is shown on Product, Plant specific products and PLPC dialogs'|| chr(10) ||''|| chr(10) ||'Yes (true) = the option is available'|| chr(10) ||'No (false) = the option is hidden', 'N');
execute CreateSystemSetting('Product Screen Settings', 'AUTOREPLACEMENT_PERC', '0', 'F', '0', 'Y', 'N', 0, 99, '', 'Defines the default value for the field Automatic Replacement in the Product/Model form.'|| chr(10) ||'If it is 0 then No Automatic Replacement is done.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'BULKPUTUP', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'In US the truck is loaded with bulk quantities. At the customer side the routeman looks at the invoice how many pieces the customer needs and takes that quantity from the bulk load in the truck. However not every item is loaded as bulk item in the truck.', 'Y');
execute CreateSystemSetting('Product Screen Settings', 'CHARGELOSSFORPOOL', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for charge loss for pool field in product dialog. Only used in LOSSFORPOOL module.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'CONFIRMPRODUCTONPDA', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'System setting is used to define if a product has the option to confirm delivery and pick up on the PDA.'|| chr(10) ||'Possible values:'|| chr(10) ||'YES - the user need to confirm pick up and delivery for all items transferred to PDA (standard behavior)'|| chr(10) ||'No - the user can de-activate the option to confirm delivered and pick up quantities on PDA'|| chr(10) ||'The default value is set on product level but can be overruled on product list per customer level.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'DEFRESVALUEPERPRODUCT', '0', 'I', '0', 'N', 'N', 0, 2, '', 'This setting is used to control whether a default residual value scheme can be defined on product level. When set to 1 or 2, the residual value scheme defined at product level will be used as a default when defining a residual value scheme on product list per customer level. If no default is defined at product level, then the standard determination process for a default will be used.'|| chr(10) ||''|| chr(10) ||'Possible values:'|| chr(10) ||'0 = No default residual value scheme can be defined at product level.'|| chr(10) ||'1 = A default residual value scheme may be defined at product level (optional).'|| chr(10) ||'2 = A default residual value scheme must be defined at product level (mandatory).', 'N');
execute CreateSystemSetting('Product Screen Settings', 'ERPPRODUCTINTEGRATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it is allowed to manually add a product Possible values:'|| chr(10) ||'0 = It is allowed to add products.'|| chr(10) ||'1 = It is not allowed to add products. In this case products are created in the ERP system and integrated into Abssolute'|| chr(10) ||'This setting is only relevant when the module ERPINTEGRATION is active.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'KEEP_DISP_STOCK', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Defines the default value for Disposable Products for the field ''Record passive Stock'' in the product form.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'KEEP_GARMENT_STOCK', 'Y', 'B', 'Y', 'Y', 'N', null, null, '', 'Defines the default value for GarmentProducts for the field ''Record passive Stock'' in the product form.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'KEEP_LINEN_STOCK', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Defines the default value for Non-Garment Products for the field ''Record passive Stock'' in the product form.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'MIN_TURNAROUND_PERC', '0', 'F', '0', 'Y', 'N', 0, 100, '', 'Defines the default value for the field minimum turnaround % in the product/model form.'|| chr(10) ||'Typically the minimum turnaround is set to a value around 40%', 'N');
execute CreateSystemSetting('Product Screen Settings', 'PACKCONTENTSEQUENCE', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the position of a pack content product within a pack is identified with the pack sequence number field or via a row and position field. Possible values:'|| chr(10) ||'0 - Use standard sequence number. Maximum value: 99999'|| chr(10) ||'1 - Use new fields to specify the position of the content product within the pack by the use of row and position.'|| chr(10) ||''|| chr(10) ||'Note: Currently only supported in the new assembly touch screen dialog.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'PACKWEIGHTCALCULATION', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether a field will be displayed in the product dialog that shows the total theoretical weight for a pack. Possible values:'|| chr(10) ||'0 - No extra field on pack product level that displays the total pack weight'|| chr(10) ||'1 - Extra field on pack product level that displays the total pack weight.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'PRODUCTSORTGROUP', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This systemsetting is used in combination with sorting system interface.'|| chr(10) ||'0 = Do not define product sort groups'|| chr(10) ||'1 = Define product sort groups and allow sorting on product sort group.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'PRODUCTTRANSPORTARTICLES', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether it should only be possible to define a max cart quantity on global product level, or if it should be possible to define a max cart quantity for each combination of product and transport article. Possible values:'|| chr(10) ||'0 - A max cart quantity must be defined at global product level '|| chr(10) ||'1 - A max cart quantity can be defined for each combination of product and transportarticle'|| chr(10) ||'This setting is only relevant when the module LOADOPTIMIZER is in the license', 'N');
execute CreateSystemSetting('Product Screen Settings', 'PUTUPTYPE', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Defines the default value for the field "put up type". For items that are not on any put up list (i.e. garments)'|| chr(10) ||'choose 1.'|| chr(10) ||'Possible values: '|| chr(10) ||'1 = Put up per customer (Packingnote)'|| chr(10) ||'2 = Bulk put up'|| chr(10) ||'3 = Bundle tag', 'N');
execute CreateSystemSetting('Product Screen Settings', 'SHOWLOSSCHARGEPERCENTAGE', '1', 'I', '1', 'N', 'N', 1, 3, '1', 'Controls which fields are shown for the Loss Charge percentage that is only used for module LOSTCHARGEPERCENTAGE '|| chr(10) ||'1 = Show percentage'|| chr(10) ||'2 = Show price'|| chr(10) ||'3 = Show price and percentage', 'N');
execute CreateSystemSetting('Product Screen Settings', 'SHOWPRODREMARKTAB', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If Yes, then an extra tab named "Remark" is shown in the Product dialog, where a description/remark about the product can be placed (up to 5000 chars).', 'N');
execute CreateSystemSetting('Product Screen Settings', 'SHOWPRODREMARKWEBTAB', 'N', 'B', 'N', 'N', 'N', null, null, '', 'If Yes, then an extra tab named "Remark for Web" is shown in the Product dialog, where a description/remark about the product can be placed (up to 5000 chars).'|| chr(10) ||''|| chr(10) ||'The field is only relevant when the module BKLINTERNET is in the license', 'N');
execute CreateSystemSetting('Product Screen Settings', 'SHOWSRCHARGEPERCENTAGE', '1', 'I', '1', 'N', 'N', 1, 3, '1', 'Controls which fields are shown for the Systematic Replacement Charge percentage that is only used for module SRCHARGEPERCENTAGE '|| chr(10) ||'1 = Show percentage'|| chr(10) ||'2 = Show price'|| chr(10) ||'3 = Show price and percentage', 'N');
execute CreateSystemSetting('Product Screen Settings', 'SOILCOUNT_LINEN', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Defines the default value for the field Is Soil Counted in the product from. This default is only used in case the type of merchandise is linen.', 'N');
execute CreateSystemSetting('Product Screen Settings', 'STRAIGHTEVENEXCHANGE', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Is straight even exchange in use'|| chr(10) ||''|| chr(10) ||'0 = Show the option in contract product and PLPC'|| chr(10) ||'1 = Do not show the option in contract product and PLPC', 'N');
execute CreateSystemSetting('Product Screen Settings', 'VOLUMEUNITPACK', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether a new field will be displayed in the product dialog that shows the total volume unit  for a pack. Possible values:'|| chr(10) ||'0 - Use standard volume unit from product logistics tab-page. Maximum value: 999'|| chr(10) ||'1 - Use new volume unit on Pack level with a maximum of 5 decimals. '|| chr(10) ||'     Maximum value: 999.99999', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'ALLOWFREQRELATEDPRICE', '0', 'I', '0', 'N', 'N', 0, 1, '', '0 = Only allow frequency related price for billing method 1, fixed delivery'|| chr(10) ||'1 = Frequency related price allowed for billing method 1, both for fixed delivery and delayed even exchange.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'ALLOWPASTENDDATE', 'Y', 'B', 'Y', 'Y', 'N', null, null, 'YN', 'It indicates whether it is allowed to enter an end date for the PLPC that lies in the past. If it is set to N then when adding a new PLPC-line or changing an existing one, it is not possible to enter an end date that is smaller than the system date. If the user tries to enter an invalid end date, a message will pop up.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'AUTOSOIL', '0', 'I', '0', 'Y', 'N', 0, 2, '', '0 = No auto soil'|| chr(10) ||'1 = Auto Soil Percentage'|| chr(10) ||'2 = Auto Soil Quantity'|| chr(10) ||'Auto soil is used for filling the soil count by default. Only for US soil count (using soil tickets).', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL1FLATRATEDRENT', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if Billing method 1 - Flat rated rent is selectable in productlist per customer', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL2RENTBASEDONMIN', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if Billing method 2 - Rent Based On Minimum is selectable in productlist per customer.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL3CIRCULATINGINV', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if Billing method 3 - Circulating inventory is selectable in product list per customer', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL3PRICETYPE', '0', 'I', '0', 'Y', 'N', 0, 3, '', '0 = Standard method, charge rent and wash'|| chr(10) ||'1 = Split price method, using split price for rent and wash.'|| chr(10) ||'2 = Split price method, charge rent only (using normal rent price)'|| chr(10) ||'3 = Split price method, charge wash only (using normal wash price)', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL4PIECERENTONLY', 'Y', 'B', 'Y', 'N', 'N', null, null, '', 'Defines if Billing method 4 - Piece Rate Only is selectable in productlist per customer', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BILL5LEASE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if Billing method 5 - Lease is selectable in product list per customer', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'BM1CHANGESPERWEEKPRICE', '0', 'I', '0', 'N', 'N', 0, 3, '1', 'This control the default value of "Changes per week" in the price control when adding a price to a billing method 1 changes per week billing price'|| chr(10) ||''|| chr(10) ||'0 = default to 0 '|| chr(10) ||'1 = default to 1'|| chr(10) ||'2 = default to *'|| chr(10) ||'3 = fixed as *'|| chr(10) ||''|| chr(10) ||'NOTE: this applies to Contract Product, PLPC and General Price List dialogs', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHARGEOVERUSEDEFAULT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default value for the checkbox "Charge Overuse" in the form "Product List per Customer".'|| chr(10) ||'Overuse billing only implemented for garments in US direct billing. ', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHARGERESVALUEFORGRADE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = No setting in PLPC (always charge res. value for all grades)'|| chr(10) ||'1 = Defined in PLPC, default ''All grades'''|| chr(10) ||'2 = Defined in PLPC, default new only (only charge res. value for new issued items)', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHARGEWASHCHG/WEEK', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, it is allowed to charge wash in combination with Billing Method 1 Changes per Week. This setting cannot be combined with ChargeWashCOGChg/Week.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHARGEWASHCOGCHG/WEEK', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Set to ''Y'' only when product is set to billing method 1, changes per week, and max inventory = changes per week (system setting CHANGESWEEKRELATEDTOMAX = 2). When set the check box Only Charge Washes for COG can be set: the'|| chr(10) ||'COG items will not be billed as rent but as wash in this case. ', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHECKPNFORENDDATE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = no action'|| chr(10) ||'1 = Warning when inactivating a product list per customer line and the related product is present on a not processed packing note.'|| chr(10) ||'2 = Error when inactivating a product list per customer line and the related product is present on a not processed packing note. Inactivating is not allowed!', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CHECKRETURNDELIVERYSCHEME', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether a validation on delivery scheme should be done upon save of a CPL line. When enabled, it must be checked if the delivery scheme of the CPL line matches the delivery scheme at PLPC level. The check should only be done for delayed-even-exchange products that have been marked for soil-count and that should be returned according to the predefined delivery scheme. Possible values:'|| chr(10) ||'0 - Do not perform this check (default)'|| chr(10) ||'1 - Perform this check upon save of a CPL line  ', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COLOR_ACTIVE', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Define text color for showing active rows:'|| chr(10) ||'0 = Black'|| chr(10) ||'1 = Red'|| chr(10) ||'2 = Purple'|| chr(10) ||'3 = Blue'|| chr(10) ||'4 = Green'|| chr(10) ||'Note: this setting is used in the productlist per customer and consumptionpointlogistics screen.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COLOR_ANNUALSTOP', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Define text color for showing active rows with an annual delivery stop:'|| chr(10) ||'0 = Black'|| chr(10) ||'1 = Red'|| chr(10) ||'2 = Purple'|| chr(10) ||'3 = Blue'|| chr(10) ||'4 = Green'|| chr(10) ||'Note: this setting is used in the consumptionpointlogistics screen.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COLOR_ENDED', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Define text color for showing inactive rows:'|| chr(10) ||'0 = Black'|| chr(10) ||'1 = Red'|| chr(10) ||'2 = Purple'|| chr(10) ||'3 = Blue'|| chr(10) ||'4 = Green'|| chr(10) ||'Note: this setting is used in the productlist per customer and consumptionpointlogistics screen.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COLOR_NOTYETACTIVE', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Define text color for showing not yet active rows:'|| chr(10) ||'0 = Black'|| chr(10) ||'1 = Red'|| chr(10) ||'2 = Purple'|| chr(10) ||'3 = Blue'|| chr(10) ||'4 = Green'|| chr(10) ||'Note: this setting is used in the productlist per customer and consumptionpointlogistics screen.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COLOR_TEMPSTOP', '0', 'I', '0', 'N', 'N', 0, 4, '', 'Define text color for showing active rows with a temporary delivery stop:'|| chr(10) ||'0 = Black'|| chr(10) ||'1 = Red'|| chr(10) ||'2 = Purple'|| chr(10) ||'3 = Blue'|| chr(10) ||'4 = Green'|| chr(10) ||'Note: this setting is used in consumptionpointlogistics screen.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COMMISSIONWEEKS', '26', 'I', '26', 'N', 'N', 0, 999, '', 'Default commssion weeks. Only used for extended commission calculation.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYEMBLEMPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if emblem prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYRENTPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if rent prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYREPAIRPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if emblem prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYREPLPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if replacement prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYSALESPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if sales prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYWASHPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if wash prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'COPYWEIGHTPRICE', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if weight prices should be COPIED or INHERITED from general price tables.'|| chr(10) ||'Fill Y for COPY, N for INHERIT.'|| chr(10) ||'Recommended use: if anniversary price increased are used (typically in US): COPY, else (for EU): inherit.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'CUSTOMERPRODLISTINVENTORY', '1', 'I', '1', 'N', 'N', 1, 3, '', '1: the inventory is defined in "Product List per Customer" (on product-customer level). (For US customers who don''t want historical adjustments). '|| chr(10) ||'2:For US customers who do want historical adjustments. '|| chr(10) ||'3: For EU customers. '|| chr(10) ||'Only applicable for rentmethod fixed quantity.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'DEFAULTONSITEINVCOUNT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Default for field ''On-site inv. count'' in PLPC', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'DEFAULTRENTMETHODGARMENTS', '3', 'I', '3', 'Y', 'N', 1, 3, '', 'Default value for the field "Charge Rent, Based on" in the form "Product List per Customer" for a garment type of product'|| chr(10) ||'1=fixed quantity'|| chr(10) ||'2=changes per week'|| chr(10) ||'3=real quantity'|| chr(10) ||'Recommended use: in US:2 , in EU:3.', 'Y');
execute CreateSystemSetting('Product List / Cust. Settings', 'DELIVERYQTYMESSAGE', '0', 'I', '0', 'N', 'N', 0, 2, '', 'If the customer has an active or future active route stop then'|| chr(10) ||''|| chr(10) ||'0 = In case a customer has only 1 department and distribution point and a product is set for fixed delivery then an error message is shown if there are no fixed deliveries entered.'|| chr(10) ||'1 = In case a customer has only 1 department and distribution point and a product is set for fixed delivery then a warning is shown if there are no fixed deliveries entered.'|| chr(10) ||'2 = No check on fixed delivery quantities.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'DELSCHEMEPERCUSTOMER', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Defines if the delivery scheme is defined in the form Product list per Customer'|| chr(10) ||'Typically for the US this setting is set to Yes, in the EU to No. In the EU '|| chr(10) ||'delivery standards are more common.'|| chr(10) ||'Note: once the table of productlist per customer contains information this setting may not be changed.', 'Y');
execute CreateSystemSetting('Product List / Cust. Settings', 'DIRECTSALEPRODUCTSALLOWED', '0', 'I', '0', 'N', 'N', 0, 1, '1', 'Controls if Product.SalesOnly YN field allows the product to be on the PLPC or Contract but forced as Billing Method 4 and Sales Only.  Or to be used in General Work Order'|| chr(10) ||''|| chr(10) ||'0 = Do not allow on PLPC, Contract Product or General Work Orders, All Products Option'|| chr(10) ||'1 = Allow on PLPC and Contract Product but only set as Billing Method 4 and Sales Only. '|| chr(10) ||' Allow it to be selected in General Work Orders, All Products Option', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'DISCOUNTACCESS', '3', 'I', '3', 'N', 'N', 1, 3, '', 'Setting for defining access to discounts: '|| chr(10) ||'1 - do not show discounts at all'|| chr(10) ||'2 - view only'|| chr(10) ||'3 - full access', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'EXTENDEDREMARKCIRCINV', '0', 'I', '0', 'N', 'N', 0, 1, '', 'Remark length on Circulating inventory Adjustment'|| chr(10) ||'0 = Maximum 60 characters'|| chr(10) ||'1 = Maximum 1000 characters', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'FIXEDWEARERSCHANGESINV', '0', 'I', '0', 'Y', 'N', 0, 1, '', '0 Number of wearers and changes is determined based on the real wearers '|| chr(10) ||'1 Number of wearers and changes is determined on the product list per customer'|| chr(10) ||''|| chr(10) ||'Important: Value 1 will change the BM1 rent calculation into:'|| chr(10) ||'Number of wearers * number of changes per week * price = Invoiced price'|| chr(10) ||'Example:'|| chr(10) ||'3 wearers * 3 chg/week * 5€ = 45€ ', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'INVWASHBASEDONSOILCOUNT', 'N', 'B', 'N', 'Y', 'N', null, null, '', 'Invoice wash based on soil count instead of delivery note.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'KEEPSALESPERSON', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y the user is obligated to enter the sales person (employee of the laundry)  in contracts of the customer and in product list per customer forms for detailed sales tracking per salesman.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'KEEPSALESPERSONCPL', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Y the user is obligated to enter the sales person (employee of the laundry) in circulating inventory line of consumption point logistics  for detailed sales tracking per salesman.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'MANDATORYPRICE', '0', 'I', '0', 'N', 'N', 0, 2, '', '0 = Prices are not mandatory, can be left empty (however it will not be possible to finalize the invoice as long as price is not defined).'|| chr(10) ||'1 = Only wash price and rent price are mandatory, if applicable.'|| chr(10) ||'2 = All prices (Wash / rent /Sales / Replacement) are mandatory when they are applicable.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'MINMAXQTYTODELIVER', '0', 'I', '0', 'Y', 'Y', 0, 2, '', '0 = Do not show fields Min Quantity To Deliver and Max Quantity To Deliver.'|| chr(10) ||'1 = Show fields Min Quantity To Deliver and Max Quantity To Deliver in Products dialog and Product Lists Per Customer dialog (only relevant for manually created delivery notes).'|| chr(10) ||'2 = Same as 1 with no default button selected.'|| chr(10) ||''|| chr(10) ||'Note: for the web application there is a separate setting MAXORDERQTYWEBPDA.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PACKWARNING', 'N', 'B', 'N', 'N', 'N', null, null, '', 'When set to Yes, this will show a warning when a pack product is added in the product list per customer. Pack contents will not be added automatically, and must be added manually if required. The warning shows all products in the pack that are not yet defined in the PLPC.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PERCAFTERDEPRECIATION', '100', 'F', '100', 'Y', 'N', 0, 100, '', 'Default value for the field "Percentage after depreciation" in the form "Product List per Customer". Only applicable when rent method is "Real quantity".'|| chr(10) ||'Percentage = percentage of RENT price.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PLPCDELETEALLOWED', '0', 'I', '3', 'N', 'N', 0, 3, '', '0 = Always allowed'|| chr(10) ||'1 = Never allowed (button not visible)'|| chr(10) ||'2 = Only future rows (not yet active plpc)'|| chr(10) ||'3 = Future rows or rows with date inactive <= Cutoffdate (invoice period closed)', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PLPCDETERMINEENDRENTDATE', '1', 'I', '1', 'Y', 'N', 0, 1, '', 'This setting controls whether the weeks in circulation at previous issues should be taken into account when calculating the end rent date when reissuing a used item. '|| chr(10) ||'Possible values:'|| chr(10) ||'0 = Do not take into account the weeks in use at previous issues'|| chr(10) ||'1 = Do take into account the the weeks in use at previous issues'|| chr(10) ||'Default value 1.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PLPCFMCHANGE', '2', 'I', '2', 'N', 'N', 0, 2, '', 'This setting controls if the finishing method for any existing packing notes and delivery notes should be changed as well changing the finishing method for a PLPC record.'|| chr(10) ||'Possible values:'|| chr(10) ||'0 - Do not change the FM for existing packing notes and delivery notes, regardless of their status'|| chr(10) ||'1 - Only change the FM for existing packing notes that have not been processed yet'|| chr(10) ||'2 - Change the FM for all existing packing notes that have not been invoiced yet', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PLPCRESETRVONREISSUE', '0', 'I', '0', 'Y', 'N', 0, 1, '', 'This setting controls whether it will be possible to define at PLPC level if the residual value of a unique item should be set to 0 when returning it to stock while it should be set to a predefined reissue price when bringing it into circulation again for another wearer. Possible values:'|| chr(10) ||'0 = Option Charge Residual value when return to stock and continue with different Residual value upon reissue is not available in PLPC dialog'|| chr(10) ||'1 = Option Charge Residual value when return to stock and continue with different Residual value upon reissue is available in PLPC dialog'|| chr(10) ||'Default value 0.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'PRICEACCESS', '3', 'I', '3', 'N', 'N', 1, 4, '', 'Setting for defining access to prices: '|| chr(10) ||'1 - do not show prices at all'|| chr(10) ||'2 - view only'|| chr(10) ||'3 - full access (by default all prices are shown)'|| chr(10) ||'4 - full access (by default only active price is shown)'|| chr(10) ||''|| chr(10) ||'only on PLPC', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'REPLACEMENTMETHOD', '2', 'I', '2', 'Y', 'N', 1, 5, '', 'Default value for the method of calculating the Systematic Replacement Charge defined in the form'|| chr(10) ||'"Product List per Customer". Typically only used in the US.'|| chr(10) ||'1=Percentage of Soil Count'|| chr(10) ||'2=Percentage of Circulating Inventory'|| chr(10) ||'3=Fixed Quantity'|| chr(10) ||'4=Percentage of billed quantity'|| chr(10) ||'5=Percentage of delivered quantity'|| chr(10) ||'Option 5 is only available as of release 9.04.03', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'SHOWDELIVERYHISTORY', '0', 'I', '0', 'N', 'N', 0, 1, '', 'This setting controls whether the Delivery History tab should be shown in the Product List per Customer dialog, or not. Possible values:'|| chr(10) ||'0 - Do not show this tab page (default)'|| chr(10) ||'1 - Do show the Delivery History tab page'|| chr(10) ||''|| chr(10) ||'This setting replaces the presence of the PLPCDELHISTORY module for controlling whether to show this tab page or not.', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'SHOWWARNINGATCHANGESALES', 'Y', 'B', 'N', 'N', 'N', null, null, '', 'When set to "Y" then a warning will be displayed in the "Change Sales Person via ZIP" dialog when the user has selected the option "Replace all sales persons".'|| chr(10) ||''|| chr(10) ||'This setting is only of any use when the system setting KEEPSALESPERSON is set to "Y".', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'SRCFREQUENCY', '1', 'I', '1', 'Y', 'N', 1, 3, '', 'Default value for the definition of the frequency of calculating the Systematic Replacement Charge (SRC), in case the calculation not based on soil count.'|| chr(10) ||'1=Every Delivery'|| chr(10) ||'2=Every Week First Delivery'|| chr(10) ||'3=Every Week Last Delivery', 'N');
execute CreateSystemSetting('Product List / Cust. Settings', 'USELOANS', 'N', 'B', 'N', 'N', 'N', null, null, '', 'Loans-tab appear only if this is setting is set to YES.  Loans can be defined using the special orders form.', 'N');