--- title: "Sales Order Related System Setting" canonical: "https://kb.myframeworks.com.au/space/FRAM/28381092/Sales%20Order%20Related%20System%20Setting" format: markdown --- # Overview The Frameworks** Sales Order Processing** (SOP) module can be customised to meet your business's specific needs. To do this, various system settings and flags can be configured to turn on or off different functionality. > ⚠️ **Important**: Only users with the appropriate security access are able to make changes to the system tables. --- ### Click on the required system setting code from more information. *Tip: Press Ctrl + f to use your browsers search function to find the system setting you are looking for.* > Macro (toc) --- # System Settings - Flags The following system flags are related to all areas of the sales order processing  > ✅ Refer to [https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28405058](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28405058) for more information on how to edit and maintain system flags. ## AutoPopCCBar **Flag/Setting Purpose:** Auto Populate Customer Contact Barcode - **When enabled**, customer contact barcodes are automatically generated and populated when creating or updating a contact record. Frameworks assigns the next available unique barcode number. - **When disabled**, barcodes are not automatically generated. You must manually enter a barcode when creating or updating a contact. The contact record is saved as entered, and barcode assignment is optional and manual. --- ## BranchMask **Flag/Setting Purpose**: Only Display Products that exist in Users Branch   - When enabled, the **Stocked Only** checkbox is enabled by default in the **Product Finder/Product Multi Selection** screen and only products in stock are retrieved. - When disabled, the **Stocked Only** checkbox is disabled by default in the **Product Finder/Product Multi Selection** screen and all products are retrieved, regardless if they are in stock or not. --- ## CopPrjLnk **Flag/Setting Purpose: **Enable Project Link On Complete of Customer Order - When enabled, the user is presented with the **Link Project** pop-up upon completing a customer order. The user has the option to complete one of three possible tasks: - Click **Create Project** to create a new project and a subsequent job within that project, and then link the new Sales Order to it, - Open the **Job Finder** and connect the new Sales Order to an existing job within a project, or - Click **Close** to exit the pop-up and continue processing the Sales Order as per normal, without linking it to an existing job or creating a new project and job. - When disabled, completing a Sales Order occurs as per normal, and the **Link Project** pop-up window will not be displayed at all. > ✅ - Refer to the [Customer Orders Processes](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30529584) for more information. > ✅ - Refer to [Projects](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383544) User Guides and [Projects Processes](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30507730) for more information. --- ## CusDryPerm **Flag/Setting Purpose: **Default Customer Diary Notes to Permanent - When enabled, sets the default value of the **Permanent** checkbox, in a **Diary Note** to be ticked. - When disabled, sets the default value of the **Permanent** checkbox, in a **Diary Note** to not be ticked. --- ## DelAreaFor **Flag/Setting Purpose: **Enforce the entry of delivery data for deliveries - When enabled, the **Delivery Area **data is required to be entered for deliveries. - When disabled, the **Delivery Area **data is not required to be entered for deliveries. --- ## DelMapForc **Flag/Setting Purpose: **Enforce the delivery area based on the map ref. - When enabled, Frameworks ensures the correct delivery area based on the **Map** **Ref** entered and makes the **Map Ref** and **Map Xref** fields mandatory when working with Sales Orders. - When disabled, Frameworks performs no validation on the **Map Ref** and **Map Xref** fields when working with Sales Orders. --- ## DelReqTime **Flag/Setting Purpose:** Enforce Entry of Requested Time - When enabled, selecting an option from the **Requested Time** drop-down field on Sales Orders is enforced. This only impacts those orders where the **Desp. Method** selected is NOT a pickup type. - When disabled, there is no requirement to select a **Requested Time** option from the drop-down on Sales Orders. --- ## FWBundle **Flag Purpose:** Frameworks Picking to use bundles - When enabled, users can allocate bundles to an order. - When disabled, bundle allocation is not available. > ✅ Refer to [FWBundle](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173542) in the Frameworks System Settings space for full details. --- ## FWBundleComment **Flag Purpose:** Saves picking group and bundle details to the transaction comment field so they appear in the Picking Dashboard. When **FWBundleComment** is enabled, Frameworks records the picking group and bundle assigned to each sales order line in the transaction comment field. Once the sales order is complete, this information surfaces in the **Picking Status** column of the **Picking Dashboard**, allowing warehouse staff to review assignments at a glance without opening individual orders. - When enabled, picking group and bundle details are saved to the transaction comment and displayed in the **Picking Status** column of the **Picking Dashboard** once the sales order is complete. - **When disabled,** picking group and bundle details are not saved to the transaction comment and do not appear in the **Picking Dashboard**. > ✅ Refer to [FWBundleComment](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173548) in the Frameworks System Settings space for full details. --- ## FWConfirm **Flag/Setting Purpose: **Enable Order/Quote Confirmation This flag enables the order confirmation functionality in Sales Orders. A notification of **ENTRY NOT COMPLETE** or **ENTRY COMPLETE** appears in the header of the Sales Order or Quote. > ⚠️ The default setting (whether enabled or disabled) for the **FWConfirm** flag is based on branch setting **Default Order Complete** (which is set under the **Branch Maintenance** activity). > ⚠️ > ⚠️ If Default Order Complete is enabled against a branch, **ENTRY COMPLETE** is automatically shown and all Orders and Quotes are automatically complete to allow a user to proceed to the next step. - When enabled, the user is able to proceed to the next step of an Order or Quote without the need to mark it as** 'Entry Complete'**, from the actions button. The **Print Options** and **Accept Quote** options will be available. - After accepting a Quote, the Sales Order is set to the value of the branch **Default Order Complete **flag. - When disabled, a newly created sales quote and order will already be marked as **ENTRY COMPLETE**. > ✅ Refer to [Branch Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28390994) for how to set this branch flag. --- ## FWUnConfirm **Flag/Setting Purpose: **Lock completed Order/Quote and allow mark as uncompleted > ⚠️ The **[FWConfirm](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173558)** flag needs to be enabled for this flag to work. - When enabled, the quote or order will be locked on **Mark as 'Entry Complete'**. To make additional changes to the order, which will affect the value if the order, you will need to **Mark as 'Entry Not Completed' **from the **Actions** menu. - When disabled, you will be able to make changes to a quote and order without the need to select **Mark as 'Entry Not Completed' **from the **Actions** menu. --- ## FWDelFeeLock **Flag/Setting Purpose: **Lock delivery fee field - When enabled, the **Delivery Fee** Field in the** Delivery Details tab** is disabled. No values can be entered and existing values cannot be changed. - When disabled, users will still be able to change the default delivery fee in the **Delivery Fee** field. --- ## FWDetCrMsg **Flag/Setting Purpose: **Display detailed credit message at POS? - When enabled, a detailed credit message is used when a customer’s credit limit is exceeded. Similar messages are displayed on both sales orders and Point of Sale transactions. - When disabled, a generic credit message is used. --- ## FWLockBpr **Flag/Setting Purpose: **Lock the SOP price on branch change in Frameworks - When enabled, the **sale price** is locked/kept if the Sales Order branch is changed. > ⚠️ The cost price will change if the branch is changed. - When disabled, the sale price will change accordingly if the Sales Order branch changes. --- ## FWLocPickPrnt **Flag/Setting Purpose: **Print product locations on Picking Slip - When enabled, the Picking Slip will show the **Primary** and **Alternate** locations for the products when using either NuVu or XML printing. > ℹ️ The Primary **** and Alternate **** locations will need to be added to your Stationery template. - When disabled, the Picking Slip will **NOT** show the Primary or Alternate locations for the products when using either NuVu or XML printing. --- ## FWLpoDepRq **Flag/Setting Purpose: **Minimum deposit required for linking purchase orders - When enabled, Frameworks prevents the linking of Purchase Order/s to a Sales Order if the customer is a cash customer and the **minimum deposit** or **minimum percentage** has not been paid on a Sales Order. These amounts are defined in **Company Maintenance **under the **Default Deposit $ **and **Deposit % Required**. Upon clicking the **Actions **button then selecting **Linked PO **in a Sales Order, a message of *"Cash customer has not paid minimum deposit of $nn. Unable to link Purchase Orders" *will be displayed*.*The minimum deposit will need to be paid via **Customer Payments** and validated via the **Credit Information** tab in the **Customer Dashboard** before you are able to link a Purchase Order to the Sales Order. - When disabled, Frameworks will allow a Purchase Order to be linked to a Sales Order and ignore any deposit requirements configured in **Company Maintenance**. > ✅ Refer In the [Create a New Company](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28405128) for more information on editing the company maintenance window --- ## FWManCusOr **Flag/Setting Purpose: **Mandatory customer purchase order numbers in use - When enabled, specific custom formats are activated for a Customer Order number. For example fields like Order No., Unit No., Address, Name and Job Number are used to make up the order number. Each field has certain requirements around length and input format as well as being optional or mandatory. These values must conform to the rules defined against each prompt. > ℹ️ To configure these custom formats, refer to **Order No. rules** in **Customer Maintenance** for further information. ![image](media://59d3c090-5219-48fd-81fd-e996d5096794) - When disabled, custom formats for Customer Order numbers are not activated. --- ## FWNegWarn **Flag/Setting Purpose: **Enable Warning Product with Insufficient Stock On POS/SOP - When enabled, a warning ⚠ will appear next to the **Product** field, when entering a product that has insufficient **Quantity Available to Pick ***(stock on hand - interim invoices - qty picked = Qty Available to Pick)*. If the product is still added to the POS or SOP transaction the **Qty **field will be highlighted red. This will be for all current orders with a product that has insufficient stock available to pick. ![image-20251021-050123.png](media://e2fea079-4a97-4764-99cd-333c27a0ad74) ![image-20251030-062115.png](media://7de9fdd5-728f-46f3-9204-15683a550bad) > ℹ️ - This **does not** stop you from adding the product to the sales order transaction. > ℹ️ - This validation does not apply to Type 6 **Miscellaneous Products**. - **When disabled**, there will be no notifications, however, stock levels will still be shown in the **Product Finder/Product Multi Selection** window or via the [Purchase Sales Information](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30507618/Viewing+Purchase+Sales+Information#Navigating-the-Purchase-Sales-Information-Window) window. --- ## FWOrdCosts **Flag/Setting Purpose: **Default value for showing costs in sales order maintenance - When enabled, a new column is displayed that shows the cost of each product in the product line and an option to hide the cost is displayed in the Actions menu. - If the user's **Cost Viewing Level **is set to **Full **the user is able to view product costs in a Sales Order transaction. The user is also able to **Hide Costs** via the **Actions** menu. - If the user's **Cost Viewing Level **is set to **Restricted **the user is NOT able to view product costs in a Sales Order transaction. The user is also NOT able to **Hide Costs** via the **Actions **menu. > ℹ️ The flag has no effect if the user is not permitted to view costs. - When disabled and the user's **Cost Viewing Level **is set to **Full **the user is not able to immediately view product costs in a Sales Order transaction, however the user is able to **Show Costs** via the **Actions** menu. > ✅ Refer to **Cost Viewing Level** for more information on changing a users cost view level. --- ## FWOrdQtyDefZero **Flag/Setting Purpose: **Default qty to 0 into Frameworks Order Line Entry - When enabled, the **quantity** of a product being added to a Sales Order defaults to **0**. - When disabled, the **quantity** of a product being added to a Sales Order defaults to **1**. --- ## OrdSFName **Flag/Setting Purpose: **Order Site Contact full Name - When enabled, the contact's **First** and **Last** name are required in the **Contact **field. - When disabled, only a contact's **First **name is required in the **Contact **field. --- ## FWPacks **Flag/Setting Purpose: **Frameworks Picking - are packs used - Use packs in Pick & Release - When enabled, the user is able to allocate **Packs** to an order and populate the tally details of a particular line with the predefined details of a pack in stock. - When disabled, **Packs** are unable to be allocated to an order. --- ## FWProjectXML **Flag/Setting Purpose: **Project quotes to output as xml document - When enabled, the **Print Quote** option within Projects will output as an xml formatted document to be applied to a template. - When disabled, the **Print Quote **option will output as a .rpt document and default to the Format 20 NuVu template. --- ## FWReqMobN **Flag/Setting Purpose: **Require mobile number on Cash Accounts - When enabled, the customer's mobile number field,** Phone (M),** mandatory when creating a new customer in SOP. - When disabled, the customer’s mobile number field is not a mandatory field when creating a new customer in SOP. --- ## FWSBuyMFG **Flag/Setting Purpose: **Restrict special buyins to manufactured products - When enabled, only **Manufactured** Products will be displayed in the Special Buy-In window when accessed in a Sales Order. A notification will read *"Only manufactured product are displayed".* - When disabled, all products will be displayed in the Special Buy-In window. --- ## FWSBuySell **Flag/Setting Purpose: **Frameworks Special Buy in to allow sell price entry - When enabled, the default value of the **Mode** field is **Fixed Sell Pricing**. - When disabled, the default value of the **Mode** field is **Pricing by GP%.** --- ## FWSOFKitComp **Flag/Setting Purpose: **Expand kits to show componentry in Sales Order Fulfilment > ℹ️ This flag is enabled by default. - When enabled, the Sales Order Fulfilment screen will expand non-exploding kits to show componentry and you will be allowed to order at the component level. - When disabled, the Sales Order Fulfilment screen still shows the kits componentry, however, you will order the kit header. ![image](media://34348822-4c68-4c5b-a799-996e73c8bc0d) --- ## FWSOPConfDDt **Flag/Setting Purpose: **Capture confirmed delivery date on Frameworks - When enabled, Frameworks will notify you that an order's delivery date has not yet been confirmed for the delivery. Order confirmation needs to occur from the **Confirm/Modify Delivery Date** option under the **Actions** menu. ![image](media://35263012-4a15-4867-80df-a4e81b140d45) - When disabled, a delivery date isn't required to be confirmed, and the order is set to **Date Confirmed** status. The option to **Confirm/Modify Delivery Date** is not showing in the **Actions** menu. ![image](media://93e5e52a-2bca-48ea-a8f8-858986669fec) --- ## FWSopConfDef **Flag/Setting Purpose: **Default Delivery Date Confirmed to no when modifying date - When enabled, on selecting **Confirm/Modify Delivery Date, **from the **Actions **menu, the **Date Is Confirmed **checkbox will always revert back to being disabled. This will force the user to re-confirm the delivery date if it was previously confirmed or enter a reason for the change. - When disabled, the delivery date confirmed checkbox will remain as it was last set. --- ## FWSopQtDelDBlank **Flag/Setting Purpose: **Allow blank delivery date on Frameworks Quotes - When enabled, the **Delivery Date** is allowed to NOT be set when working with Quotes. - When disabled, the Delivery Date field is required to be populated when working with Quotes. --- ## FWSopQtDespBlank **Flag/Setting Purpose: **Allow blank despatch method on Frameworks Quotes - When enabled, the **Despatch Method **is allowed to NOT be set when working with Quotes. - When disabled, the Despatch Method** **must be populated when working with Quotes. --- ## FWSOPRelAll **Flag Purpose:** Allow for a release all function in SOP The **FWSOPRelAll** flag controls the Quick Release function during Pick and Release in Sales Order Processing. When enabled, the system prompts you to decide whether to backorder before picking begins, with the option to auto-pick all lines and skip straight to the order release. - **When enabled**, on selecting **Pick and Release** from the **Actions** menu in the [Sales Order Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28408932) screen, you're prompted with the question "*Do you need to backorder?*" If the answer is **No**, the system fills out the picking details with everything being picked and goes straight to the **order release** window. If the answer is **Yes**, the system opens the picking screen as usual. - **When disabled**, Pick & Release is handled as normal without the backorder prompt. > ⚠️ If the branch on the sales order has **Stock By Location** enabled in [Branch Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28390994), the "*Do you need to backorder?*" prompt is suppressed and no automatic picking occurs. The **Pick and Release** screen opens without the prompt and you complete picking manually. > ⚠️ > ⚠️ This prevents transaction lock issues that occurred when no location was selected during auto-picking at location-controlled branches. > ⚠️ > ⚠️ The **Stock By Location** setting requires the **LOC** feature code to be active for location control to function. > ⚠️ > ⚠️ **Related settings and documentation:** > ⚠️ > ⚠️ - [Branch Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28390994) - **Stock By Location** setting. > ⚠️ - [Pick and Release](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30528860) - picking workflow. > ⚠️ - [Pick and Release Related System Settings](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28402618) - related system flags. --- ## FWSPECPOS **Flag/Setting Purpose: **Enable the Create of Special product popup for POS - When enabled, a **Special Product **button will be available from the Point of Sale screen. This is accessible from the **Actions** menu in the bottom right corner of the screen. - When disabled, the **Special Product** button is hidden from view on the Point of Sale screen. --- ## FWSplitTrn **Flag/Setting Purpose: **Enable splitting of transactions in SOP - When enabled, the **Split Transaction **option will be available from the **Actions **menu. This will allow you to select which product you want to move into a separate SOP transaction. > ⚠️ For this functionality to work correctly, the **FWSplitTrn **flag must be enabled, no Purchase Orders should be linked to the transaction, and picking must not be in progress (it is available before and after picking). - When disabled, this function will not be available from Sales Order maintenance. --- ## FWWorkBrnHdr **Flag/Setting Purpose: **Default workorder lines to branch on header - When enabled, the Branch will default to the Branch defined in the Work Order's header for the **Product Stock In **and** Out **windows. - When disabled, the Branch will default to the users logged in Branch for the **Product Stock In **and** Out **windows. --- ## GPLineSOP **Flag/Setting Purpose: **Allow GP per Line in POS - When enabled, it allows you to reprice an individual product line based on a new GP% entered by a user. Repricing an individual product will re-price the product sell based on the current unit cost of the product line. Any previously existing discounts will be overridden as part of this process. For example, if a product had an existing *Discount %* of 10% and you applied a new *GP%*, the *Discount % *resets to 0. - When disabled, the ability to reprice an individual product line based on a new GP is not shown to the user when editing a Sales line. > ✅ Refer to operation guide: [Reprice an Individual product in SOP based on a new GP%](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30520334) for further information. --- ## InvUsageBR **Flag/Setting Purpose: **Invoices sort by usage - When enabled, product lines printed on invoices are grouped by usage description, which is entered into the **Usage** column on Sales Order lines. - When disabled, product lines printed on Invoices are add by line number. > ⚠️ The Invoice stationery needs to be set to NuVu Format 20. > ✅ Refer to [Stationary Formats](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401568/System+Control+File+Maintenance#Stationery-Formats-Tab) for more information on Format 20 Invoices --- ## OrdDefAddr **Flag/Setting Purpose: **Default customer address for delivery in Orders/Quotes - When enabled, the delivery details will auto-populates in a Sales Order with a Customer's default customer address details defined in **Customer Maintenance**. - Additionally, the default customer address is displayed in the **Invoice To** header field on a printed Credit Invoice (***applies to Credit Invoices only***). - When disabled, the delivery details will NOT auto-populates in a Sales Order with a Customer's default customer address details defined in **Customer Maintenance**. --- ## OrdDelFee **Flag/Setting Purpose: **Customer Delivery Fee overrides Area Selected Fee - When enabled, the **Customer Delivery Fee** overrides the **Area Selected Fee**. - When disabled, the Area Selected Fee overrides the Customer Delivery Fee. --- ## OrderDel **Flag/Setting Purpose: **Default the sales order delivery date to today. > ⚠️ **Note:** This flag works in hand with **[OrderDelDt](#)****.** - When enabled: - If the system flag **OrderDelDt **is disabled and **OrderDel **is enabled, all date fields default to **today's date** - When disabled: - If the system flag **OrderDelDt **is enabled and **OrderDel **is disabled, all date fields default to **blank** - If the system flag **OrderDelDt **is disabled and **OrderDel **is disabled, all date fields default to **tomorrow** (that is today +1) > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13176278](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13176278) --- ## OrderDelDt **Flag/Setting Purpose: **Default the sales order delivery date to zero. > ⚠️ **Note: **This flag works in hand with **[OrderDel](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186709)****.** - When enabled: - If the system flag **OrderDelDt **is enabled and **OrderDel **is disabled, all date fields default to **blank** - When disabled: - If the system flag **OrderDelDt **is disabled and **OrderDel **is enabled, all date fields default to **today's date** - If the system flag **OrderDelDt **is disabled and **OrderDel **is disabled, all date fields default to **tomorrow**, (that is today +1) > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186709](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186709) --- ## OrdNegSell **Flag/Setting Purpose: **Allow negative sell prices to be entered in both POS and SOP - When enabled, negative sell prices are allowed to be entered for products on POS and SOP transactions. - When disabled, you are prevented from being allowed to enter a negative sell price of a product on POS and SOP transactions. --- ## OrdNewDfQt **Flag/Setting Purpose: **Default new transactions to quotes - When enabled, new transactions created by clicking the **New** button in sales orders defaults to **Quotes**. - When disabled, new transactions created by clicking the **New** button in sales orders defaults to **Order**. --- ## OrdPrjDfQt **Flag/Setting Purpose: **Default new transactions to quotes when created from Projects - When enabled, new transactions created in sales orders from a project defaults to **Quotes**. ![image](media://2c803331-628a-47d2-998d-0dcdb862b4c8) - When disabled, new transactions created in sales orders from a project defaults to **Order**. --- ## OrdReasOpt **Flag/Setting Purpose: **Price override reason is optional for FW Sales Order - When enabled, the** Override Reason** field is set as **optional**. - When disabled, the** Override Reason** field is set as **mandatory**. --- ## OrdReasOp2 **Flag/Setting Purpose: **Make the price override reason optional only on price increases in SOP (works with **[OrdReasOpt](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13175873)**). - When enabled, the** Override Reason** field is set as **optional** only for price increases, increased via the **Unit Price** field in SOP, POS and Interim Invoices. - If **OrdReasOpt** is disabled, for price decreases, the **Override Reason** field is still mandatory. A message “***A price override reason must be selected***” or “***You must enter a valid price override reason***” is displayed. - When disabled, --- ## OrdRtnDelPup **Flag/Setting Purpose: **Retain delivery details for pickup orders - When enabled, the Delivery Address Details of a transaction will be retained even if the Despatch Method was changed from Delivery to Pick Up. - When disabled, the address fields are wiped out/replaced when the despatch method is changed. --- ## OrdSByFWPX **Flag/Setting Purpose: **When creating a special buyin in Frameworks, if the flag (OrdSByFWPX) is set to yes we need to also set the trnmas.is_special_buy_in field to yes. - When enabled, Frameworks allows the entire order to be flagged as a special buy-in, rather than on a line by line basis. - When disabled, special by-ins are only available on a line by line basis. There is no option to flag the entire order as a special buy-in. --- ## OrdUsagVal **Flag/Setting Purpose: **Validate Order Usage Codes in Sales Orders - When enabled, the **Usage** code on a sales order must be predefined via the **Job Tables - Job Usages **as Frameworks validates the usage code when adding a product. ![image](media://dd480444-ef68-4606-99a7-946354c52967) - When disabled, the **Usage** codes is able to be entered as free form text, and is NOT validated when a product is added. > 📝 **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173328](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173328) --- ## PickSlipPrtBin **Flag/Setting Purpose: **Enable printing copies from different printer trays for picking slips. - When **enabled**: - The **Use Multiple Printer Trays** checkbox appears in the print dialogue when printing picking slips. - When checked, each copy prints as a separate print job to sequential printer trays (tray 1, tray 2, tray 3, tray 4), supporting colour-coded pick slip workflows. - Maximum of 4 copies can be distributed across different trays. If more than 4 copies are specified, all copies print from the default printer tray only. - If the **Use Multiple Printer Trays** checkbox is unchecked, all copies print from the default printer tray. - When **disabled**: - All picking slips print from the default printer tray regardless of the number of copies specified. - The **Use Multiple Printer Trays** checkbox does not appear. > ⚠️ **Prerequisites:** Configure picking slip stationery for XML Nuvu format, enable QZ Tray browser printing and use multi-tray printer hardware. --- ## PosGtin **Flag/Setting Purpose: **Select UOM at POS/SOP when a GTIN is scanned - When enabled, a **UOM** popup screen will be available upon entry of a GTIN marked for **sales** in SOP. - When disabled, for products with GTINs entered in Sales Orders, the GTIN will be automatically entered and locked. --- ## PRJSectSort **Flag/Setting Purpose: **Sort Project Quotes by section code - When enabled, the section on a printed Project Quote will be sorted by using the **Section Code** instead of the Section Description. - When disabled, the section on a printed Project Quote will be sorted alphabetically by using the **Section Description** instead of the Section Code. --- ## ProdCustDescCnf **Flag/Setting Purpose: **Use Customer Friendly Description for Products - Order Confirmation - When enabled, a customer friendly product description is displayed on an order confirmation instead of the default product description. - If the customer description is blank, defaults to the product description on **ALL** stationery. - When disabled, default\normal product descriptions will be displayed on an order confirmation. > ℹ️ **For XML printouts ONLY.** --- ## ProdCustDescDel **Flag/Setting Purpose: **Use Customer Friendly Description for Products - Delivery Docket - When enabled, a customer friendly product description is displayed on a delivery docket instead of the default product description. - If the customer description is blank, default to the product description on **ALL** stationery. - When disabled, default\normal product descriptions will be displayed on a delivery docket. > ℹ️ **For XML printouts ONLY.** --- ## ProdCustDescInv **Flag/Setting Purpose: **Use Customer Friendly Description for Products - Invoice - When enabled, a customer friendly product description is displayed on an invoice instead of the default product description. - If the customer description is blank, default to the product description on **ALL** stationery. - When disabled, default\normal product descriptions will be displayed on an invoice. > ℹ️ **For XML printouts ONLY.** --- ## ProdCustDescPsl **Flag/Setting Purpose: **Use Customer Friendly Description for Products - Picking Slip - When enabled, a customer friendly product description is displayed on a picking slip instead of the default product description. - If the customer description is blank, default to the product description on **ALL** stationery. - When disabled, the default product description is displayed as per normal. > ⚠️ If the customer description is blank, default to the product description on **ALL** stationery. > ℹ️ **For XML printouts ONLY.** --- ## ProdCustDescQte **Flag/Setting Purpose: **Use Customer Friendly Description for Products - Quote - When enabled, a customer friendly product description is displayed on a quote instead of the default product description. - If the customer description is blank, default to the product description on **ALL** stationery. - When disabled, default\normal product descriptions will be displayed on a quote. > ℹ️ **For XML printouts ONLY.** --- ## PSlipCalc **Flag/Setting Purpose: **Calculate unalloc qty in Picking Slip > ℹ️ **This flag is enabled by default.** - When enabled, this calculates unallocated quantities in a Picking Slip. The default setting is activated. When printing Picking Slips using Format #20 / Nuvu, the system was performing a large calculation for unallocated quantities. If a site has a large volume of transactions for some/all products, this calculation can take an excessive time to complete due to it's complexity. **PSlipCalc** is used so large volume sites can skip this calculation and avoid delayed processing during the printing of Picking Slips in Format #20. - When disabled, the system will not call the recalculation of unallocated quantities. --- ## PSlpSumm **Flag/Setting Purpose: **Print summary on Picking Slip - When enabled, the picking slip includes a summary section that consolidates all kit component products and individual products on the order by location. - When disabled, a summary section will not be printed on a picking slip.
Click here to see report examples.
--- ## QuoteFW **Flag/Setting Purpose: **Add Option to print consolidated quote > ℹ️ **This flag is disabled by default.** - When enabled, a **Consolidate Products** checkbox option will be available from the **Output Dialog** window. This allow products with the same **Product No.**, **UOM **and **Discount Price** on a quote to consolidate into a single line on the **Printed Quote** file. - When disabled, there will be no consolidate products option.
Click for an example In the example below, product 00760034 will be consolidated into a single line on the print file as the *Product No*., *UOM* and *Discount Price* match, however product 00580021 will not be consolidated as the *Product No*. & *UOM* match, however the *Discount* *Price* does not. ![image](media://193894dd-3bd5-4853-b57e-348424ca3fd6) Enable the **Consolidate Products** checkbox to consolidate products with the same *Product No*., *UOM* and *Discount Price* to consolidate into a single line on the print file. Product 00760034 has been consolidated in the report, whereas product 00580021 was not consolidated in the report: ![image](media://23ba8178-f384-429d-8246-fb581ea9085c)
--- ## RecCashEml **Flag/Setting Purpose: **Force collection of email address when creating cash card customers in POS and SOP - When enabled, it forces the sales person to collect an email address when creating cash card customers in Point of Sale (POS) and SOP. - When disabled, transactions in Point of Sale (POS) and SOP behave as normal for cash card customers. --- ## SOFDefaultReq **Flag/Setting Purpose: **Default Sales Order Fulfilment Source to Requisition - When enabled, the Sales Order Fulfillment **Source** defaults to purchase **Requisition **for the preferred supplier. > ℹ️ The **[SOFSkipExcess](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178968)**** **flag should be enabled if you always want the source to default to **Requisition.** - When disabled, the Sales Order Fulfillment **Source** defaults to **Purchase Order **for the preferred supplier. > ℹ️ **Related Flags: **[https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178968](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178968) --- ## SOFSkipExcess **Flag/Setting Purpose: **Skip checking of excess stock when loading SO Fulfillment - When enabled, the sales orders fulfilment screen will NOT search for branches with excess stock upon loading the Sales Order Fulfillment screen. - When disabled, the sales orders fulfilment screen searches for branches with excess stock upon loading the Sales Order Fulfillment screen (dependent upon **[FWAutoBTExcess](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13172941)****, ****[FWForceBTExcess](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13174252)**** and ****[InvExBrStk](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186043)**** **flag settings). > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13172941](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13172941) [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13174252](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13174252) [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186043](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186043) > ✅ Refer to [Excess Stock Auto Branch Transfer - Setup and Configuration](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382368) for more information. --- ## SONewPopup > ℹ️ This flag is enabled by default from version 5.10+. **Flag/Setting Purpose: **Pop-up dialogue when entering a new Sales Order header details - When enabled, a **New Sales Order **pop-up window will open to enter the new sales quote/order header details. - When disabled, the **Order Maintenance** screen will open for the header details to be entered. --- ## SOPConfDDt **Flag/Setting Purpose: **Capture confirmed delivery date on Sales Orders - When enabled, users are prompted to confirm delivery date on quote acceptance. - When disabled, --- ## SOPDDktBdl **Flag/Setting Purpose: **Delivery Docket sort by bundle - When enabled, the delivery dockets are sorted by their bundle numbers. - When disabled, delivery dockets are sorted chronologically by their line number (default). --- ## SOPDupCOrd **Flag/Setting Purpose: **Check for duplicate customer order numbers in SOP - When enabled, the validation process of checking for duplicate **Cust Order #** will include all sales transactions (quotes, orders and invoices) and Customer Orders transaction numbers. - For Sales transaction, you will receive the warning message  ⚠ *‘Duplicate order number exists’* an option to **View the Transactions** or **Continue to Save**. - For Customer Orders transaction, you will receive the warning message  ⚠ *‘Customer order number already in use for Customer Order: [Customer Order No.]'*. - When disabled, the validation process will NOT look up Customer Orders transaction numbers when the Customer Maintenance flag **Order Number Unique **has been enabled. > ⚠️ **NOTE**: If the **Customer Maintenance** flag **Order Number Unique **has been enabled, you will receive an error and you will need to enter a unique customer order number to save the order. > ✅ Refer to [Customer Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28389894) for more information on **Order Number Rules **and the **Order Number Unique **flag. --- ## SOPMiscCostEdit **Flag/Setting Purpose: **Allows editing of cost on miscellaneous products in Sales Order Processing. - When enabled, it allows editing of cost on miscellaneous products in Sales Order Processing. - In the **Special Buy-in** popup, the **Cost** field is editable, and certain fields like **Supplier Code**, **Supplier Reference**, and **Expiry Date** are optional. - In **Template Kit Maintenance**, cost changes on miscellaneous products, without needing to enter values for **Supplier Code**, **Supplier Reference**, and **Expiry Date** fields. > ℹ️ For non-miscellaneous products added or edited in the **Special Buy-in** popup, the current rules and functionalities will continue to apply. - When disabled, the current functionality applies to the supplier code, supplier reference, and expiry date --- ## SOPPG20 **Flag/Setting Purpose: **Picking Slip sort By Picking Group - When enabled, the picking slips are sorted by picking groups. - When disabled, picking slips are not sorted. --- ## SOPPG20Brk **Flag/Setting Purpose: **Break picking slip page by Picking group - When enabled, the picking slips are printed with a page break for each picking group. - When disabled, picking slips are printed normally with no page breaks. --- ## SOPQtePric **Flag/Setting Purpose: **Disable PRICES option when printing quotes in SOP - When enabled, and **Discount Percentages**, from the **Disc %** field on the Quote, will NOT be displayed on Quotes when the **Show Prices** option is checked on the **Output Dialog **window. - When disabled, any **Discount Percentages**, from the **Disc %** field on the Quote, will be displayed on Quotes when the **Show Prices** option is checked on the **Output Dialog **window. > ✅ Refer to [Printing, Emailing or Faxing Stationery from Frameworks](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30517140) for more information about the **Output Dialog **window. --- ## SOPRetBT **Flag Purpose:** Retain Branch Transfer supplier on special buy-in supplier selections The **SOPRetBT** flag controls whether the supplier on a sales order or quote line is replaced when using the special buy-in function. The SOPRetBT flag only applies when the current supplier is an internal branch (branch transfer supplier). For all other supplier types, the special buy-in supplier always replaces the existing supplier regardless of the SOPRetBT flag setting. - **When enabled,** the internal branch transfer supplier is retained on the sales order or quote line when a special buy-in supplier is selected. The cost on the line is still updated from the special buy-in contract, but the supplier remains as the internal branch. - **When disabled (default),** the internal branch transfer supplier is replaced by the special buy-in supplier. The cost is updated from the special buy-in contract. --- ## SOPSpecCrd **Flag/Setting Purpose:** Prevents credit notes for special products if there is no corresponding supplier return. - When enabled, a stock return credit note to a customer cannot be generated if the product has not had a supplier stock return created for the product. > ⚠️ This error message is displayed if the flag is enabled, “*Product [999999999] is a Special Purchase and a return to the supplier has not been created. This product cannot be credited to the customer.”* - When disabled, a stock return credit note to a customer can be generated even if the product has not had a supplier stock return generated. --- ## SOPSPReuse **Flag/Setting Purpose: **Disallow the re-use of specials created - When enabled, the user is NOT able to add a special product to a Sales Order. - When disabled, the user is able to add a special product to a Sales Order. --- ## SOPSupDet **Flag/Setting Purpose: **Accept Supervisor Details when Accepting a Quote? - When enabled, a user is prompted to enter supervisor details at Quote Acceptance. - When disabled, the Supervisor Name and Phone fields are not shown on the Quote Acceptance screen. --- ## SOPUomPrcWrn **Flag/Setting Purpose: **Warn to reprice order if uom changed for price overrides - When enabled, if the UOM is changed on a product line that has a price override (pricing method), you will receive a warning message that the *"Line should be repriced"*. - When disabled, no warning message will be displayed when product line's UOM is updated. --- ## SOPUsageBr **Flag/Setting Purpose: **Format 20 Quotes sort and break by Usage - When enabled, Quotes set to NuVu Format 20 are sorted and broken down by Usage. - When disabled, Quotes set to NuVu Format 20 will not be broken down by Usage. > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178069](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178069) > ✅ Refer to [Stationary Formats](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401568/System+Control+File+Maintenance#Stationery-Formats-Tab) for more information on Format 20 Quotes. --- ## SOPUsageSBr **Flag/Setting Purpose: **Quotes sort by usage sequence number - When enabled, quote printouts sort by usage sequence number. If both **SOPUsageBR **and** SOPUsageSBr** are both active, **SOPUsageSBr **(usage sequence numbers) takes precedence. - When disabled, quote printouts will not be sorted by usage sequence number. > ℹ️ For Quote set to **Output XML, **delivery fees or any other product without a linked usage will be displayed at the bottom of the quote after the usage sequence. > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178634](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13178634) > ✅ Refer to [Stationary Formats](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401568/System+Control+File+Maintenance#Stationery-Formats-Tab) for more information on Output XML for Quotes. --- ## SOPUsgePrt **Flag/Setting Purpose: **Print usage heading on quotes picking slip - When enabled, quotes & picking slips print a usage heading on them. - When disabled, quotes & picking slips will not be printed with a usage heading. **Example Reports based on flag settings:**
The Usage heading is printed on a Quote & headings and products are not sorted alphabetically **Setup Required**: - **SOPUsagePrt**:** **enabled - **SOPUsageBr**: disabled - **Quote Stationary Setting**: 02 ![image](media://2d1f8dc1-f37d-4d30-82c3-655ec2e3ce07)
When printing a Quote, products are consolidated by product groups and products under product group are sorted by product code **Setup Required: ** - **SOPUsagePrt**:** **enabled - **SOPUsageBr**: disabled - **Quote Stationary Setting**: 02 ![image](media://bd9409e0-e7c1-4e42-a258-f328a571fd85)
The Usage heading is printed without sorting alphabetically and products per usage are not sorted when printing a picking slip **Setup Required: ** - **SOPUsagePrt**: enabled - **SOPUsageBr**: disabled - **Picking Slip Stationary Setting**: 02 ![image](media://eba9b0e2-fdfe-4c4a-9636-a6b02ef926d7)
--- ## SpcItmBcode **Flag/Setting Purpose: **Controls whether the Barcode field is required when creating a Special Product in Sales Order Processing (SOP) and Point of Sale (POS). **Possible Values:** - When set to **Not Required**, the Barcode field does not appear in the Special Product creation window. - When set to **Optional**, users may enter a barcode or leave the field blank. - When set to **Mandatory**, a barcode must be provided before the Special Product can be saved. If the auto-generation flag ([SpcItmGenBcode](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/73203739)) is enabled, the system will generate a unique barcode automatically. --- ## SpcItmGenBcode **Flag/Setting Purpose:** Automatically generates a unique barcode for Special Products when they are created in Sales Order Processing (SOP) or Point of Sale (POS). > ⚠️ If [SpcItmBcode](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/73138214) is set to "Not Required," this flag has no effect (the field is hidden) **When Enabled:** - The system automatically fills the Barcode field for new Special Products. - If a supplier barcode exists, it is used; otherwise, a unique barcode is generated. - Ensures every Special Product has a barcode, supporting EDI and reducing manual entry. **When Disabled:** - You must enter the Barcode manually if required by SpcItmBcode. - No automatic barcode generation occurs. --- ## SysMobFrc **Flag/Setting Purpose: **Force Mobile number on Site Contact Phone - When enabled, the **Contact Phone **field becomes mandatory when creating a new order or modifying an existing order. - The following **System Settings** are required to be defined for validation when SysMobFrc is enabled. - **System Setting - General**: SysMobPre - Defines the allowed number prefixes. - **System Setting - Numeric**: CusPhLen - Defines the required number length. - When disabled, the **Contact Phone **field is NOT mandatory and the above validations are NOT used, even if defined. --- ## TimVal **Flag/Setting Purpose: **Timber length validation by product - When enabled, it validates product timber lengths either at the system level or at the product level. If a timber length is invalid, an error message “***Invalid Product Length (.nn)*****” **appears. If timber lengths are defined at both the system and product level, the product level takes precedence. - When disabled, no validation occurs when adding timber lengths. --- ## WHouseSupDef **Flag/Setting Purpose: **Use Warehouse Supplier as Default - When enabled, processing a Purchase Requisition, the Supplier for a Stocked Product defaults to the Internal Supplier of the Warehouse Branch. If the Product is Not Stocked, it still defaults to the Preferred Supplier. - When disabled, --- ## XMLPickMLocn **Flag/Setting Purpose: **Output Multiple locations on the XML - When enabled, an additional four locations are able to be outputted to the XML Picking Slip and XML Put Away Dockets. The extra tags for the XML output are: - - - and - - When disabled, the XML Picking Slip and XML Put Away Dockets. only support 2 location tags for the XML output (which are and ). --- ## XMLTallyTextB **Flag/Setting Purpose: **Add bold trigger to tally text - When enabled, the quantities and lengths (**qty/length**) text of a tally product will be presented in bold for the following XML outputs. - Project Quote - Sales Quote - Order Confirmation - Picking Slip - Delivery Docket - Invoice - Statement - Customer Transaction Detail Enquiry - When disabled, the quantities and lengths (qty/length) text of a tally product will NOT be presented in bold. # System Settings - Numeric The following system numeric settings are related to all area's of the sales order processing  > ✅ Refer to [System Settings - Numeric](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401694) for more information on how to edit and maintain system numeric settings. ## CusPhLen **Setting Purpose: **Standard Length For Customer Phone Number. > ℹ️ The System Setting - Flag **SysMobFrc** is required to be enabled. Enter the required mobile/phone number length into the **Value **field. Typically mobile numbers are 10 digits in length. --- ## FWDelDays **Setting Purpose**: Number of days for allowing historical delivery dates on orders and quotes Sets the number of days (via the **Date Required** and **Delivery Date** fields) to specify the allowable historical delivery dates on Sales Orders and Quotes. ![image](media://0fabae39-673d-4b38-bc0c-a122595743af) ![image](media://67da56ff-6a80-4a6b-ab46-7a28bf284214) --- ## FWLPODays **Setting Purpose**: Number of days to adjust created linked POs in SOF This is used to set the **Linked Purchase Order delivery days.** If setup, the **Date Required** field in the Sales Order Fulfillment (SOF) screen/s defaults to the **Delivery Date** **Reqd **field on the Sales Order minus the number of days specified by this flags value. > ℹ️ If the Sales Order Date minus the FWLPODays is less than the Current date, then the Linked Purchase Order date required will be set to the current date instead of the date already past. --- ## OrdQComSiz **Setting Purpose**: Field size of comments on Quote To enable, enter a **Value** to specifies the number of characters, for example 100, allowed in the **Comments **field of products. This is then transferred to the **Description **field of quotes that have been emailed. If the **Value **is **0 **this setting is disabled. # System Settings - General The following general system settings as are related to all area's of the sales order processing  > ✅ Refer to [System Settings - General](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382808) for more information on how to edit and maintain general system settings. ## BOWMAJIC **Setting Purpose:** Default Despatch Method for Majic Invoices import. The **BOWMAJIC** setting defines the default despatch method applied to sales orders created via the Majic Invoice Import task. - In the **Value** field, enter the **[Despatch Methods](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383350)** code for the despatch method to be used (for example, DEL). Leave the value blank to apply no default despatch method to imported orders. --- ## OrdTfrDesp **Setting Purpose**: Default despatch method for branch transfers Enter the **[Delivery - Despatch Types](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383350)**** code** in the **value **field to automatically populates the required **Despatch Method** for **branch transfers** created from linked Purchase Orders. > ✅ Refer to [Delivery - Despatch Types](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383350) for more information. --- ## OrdTfrArea **Setting Purpose**: Default delivery area for branch transfers Enter the **Delivery Area **in the **value **field to automatically populates the **Delivery Area **for **branch transfers** created from linked Purchase Orders. --- ## PODrctDel **Setting Purpose**: Shipping basis code to be used on direct delivery purchase orders Enter the **System - Shipping Basis Code **in the **value **field to automatically populates the **Shipping basis code **for direct delivery purchase orders. --- ## SOPChBkDel **Setting Purpose**: Despatch method for chargeback transactions Enter the **Despatch Method**, in the **Value **field for **chargeback** transactions. Create the  unique despatch type under [Despatch Methods Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383350) in Miscellaneous Table Maintenance. > ℹ️ The despatch type should not have delivery, Pick Up or P and D flags enabled - it is only meant as an internal despatch type. --- ## SOReqTime **Flag/Setting Purpose:** Default requested time for Sales Orders - Enter a **Requested Delivery Times code** into the **Value** field. This will set a default value in the **Requested Time** field when creating a new sales quote, order, or POS transaction. If this field is left blank, no default value will be set. ![image-20241101-005347.png](media://65ece1b4-1f18-48b8-b8b5-03d581a01019) > ℹ️ **Note:** Request Times MUST be defined first in the **Requested Delivery Times** table. --- ## SopChBkProd **Setting Purpose**: Placeholder product code for chargeback transactions Enter a **Miscellaneous Product Code**, in the **Value** field, then when a chargeback order is created the Sales Order and Purchase Order will be created with this product. > ✅ Refer to [Creating a New Product](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30509628) for more infromation on creating a miscellaneous product type. --- ## SopDrctDel **Flag/Setting Purpose**: Despatch Method for Direct Delivery Enter the **[Despatch Methods Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28383350)**** code** in the **value **field to define the **Despatch Method **used for direct delivery purchase orders. This setting works in conjunction with **PODrctDel**, which defaults the **Shipping Basis Code** on the Purchase Order when a direct delivery despatch method is set on a sales Order > ℹ️ **Instruction **informaion, form the Sales Order, are copied from a Sales Order to the linked Purchase Order for orders that have the "Direct Delivery" **Despatch Method** assigned. --- ## SpcItmLoad **Setting Purpose**: Special Product Creation - Cost Loading Field - ("Not Required", "Optional", or "Mandatory") Enter **Not Required, Optional** or **Mandatory **in the **Value **filed to define the **Cost Loading** field in the **Create Special Product **window. --- ## SpcItmSubG **Setting Purpose**: Special Product Creation - Product Sub Groups Field - ("Not Required", "Optional", or "Mandatory") Enter **Not Required, Optional** or **Mandatory **in the **Value **filed to define the **Product Sub Groups **field in the **Create Special Product **window. --- ## SpcItmSupl **Setting Purpose**: Special Product Creation - Supplier Field - ("Not Required", "Optional", or "Mandatory") Enter **Not Required, Optional** or **Mandatory **in the **Value **filed to define the **Supplier **field in the **Create Special Product **window. --- ## SpcItmWast **Setting Purpose**: Special Product Creation - Wastage Field - ("Not Required", "Optional", or "Mandatory") Enter **Not Required, Optional** or **Mandatory **in the **Value **filed to define the **Wastage **field in the **Create Special Product **window. --- ## SpcItmWhse **Setting Purpose**: Special Product Creation - Location Field - ("Not Required", "Optional", or "Mandatory")  Enter **Not Required, Optional** or **Mandatory **in the **Value **filed to define the **Location** field in the **Create Special Product **window. --- ## SysMobPre **Setting Purpose: **List of valid mobile number prefixes. > ⚠️ The System Setting - Flag **SysMobFrc **is required to be enabled. Enter the list of allowed mobile number prefixes into the **Value **field, for example, 04 would only allow mobile numbers starting with 04 to be entered into the contact number field > ℹ️ Multiple prefixes can be added with a comma separating them, for example, **04,05. ** --- # Additional Information > ✅ Refer to the [Sales](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28377134) User Manual for more information relating to the Sales module. > ✅ > ✅ Refer to [Miscellaneous Table Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401684) for further information on System Flags.