Skip to main content
Skip table of contents

Sales Orders - Known Issues

Known issues and quirks in the Sales Order screen.

An issue appearing in this list does not guarantee development priority. If you are having issues caused by a known issue please have your implementation partner raise a case referencing the Issue ID.

Changing Default Location repeatedly doesn’t prompt to update all lines after first update.

Issue ID: CE00050692

Status: By Design.
When you change the default location on an order repeatedly, you are only prompted to update sales order lines on the first update.

This is by design to reduce the number of prompts sent to a user. It is assumed that a user repeatedly changing the default location is intending to enter new lines with that default, rather than update existing lines on an order.

Sales Order Extra Field info flows through to wrong lines in DR_INVLINES if show all isn’t used during multiple supply.

Issue ID: EXB-6688

if you have extra fields at the line level on a sales order line and partly process the order.  If you then untick the Show All button when supplying the next delivery for that order, the extra field info goes through to the wrong line on the invoice 

Workaround

Do not untick “Show All” when doing a repeated supply/process on a sales order as this can lead to fields being misaligned. It is possible to trigger data using database identifiers.

Restricted good checks do not apply correctly when Supply or Quick Supply actions are used instead of save.

Issue ID: EXB-6589

In some circumstances, using Supply or Quick Supply actions on a sales order can allow restricted items to be recorded for sale to debtors who should be restricted from purchase.

Workaround

Add a business alert to enforce restricted items logic, an example of possible logic you might use in a Sales Order Save type event is:

SQL
WITH RES AS
(
SELECT STOCKCODE,[DBO].[FN_RESTRICTED_ITEM] (@l.STOCKCODE, @ACCNO, -1, -1, 1, -1, -1) RESTRICTED
FROM SALESORD_LINES  
WHERE HDR_SEQNO = @ORDERNO
)
SELECT * FROM RES WHERE RESTRICTED = 'Y'

Please check any business alerts meet your business requirements before applying, also consider writing a more direct SQL query than the above, as use of database functions is likely to provide worse performance than direct table joins.

Prompt Payment discounts cannot be applied to credit notes/reversals.

Issue ID: EXB-6593

When allocating Credit Notes to Invoices, the prompt payment discount box is available, however using it won’t generate any change to credits/allocations. This is misleading.

Workaround

Separately generate a debit note to act as a reversal of the original prompt payment discount

Stored POSLAYBY PDF document is overwritten with the content of .CLE email template if document is printed and emailed

Issue ID: EXB-6611

When printing a POSLAYBY.CLF form for a Layby in Exo Point of Sale, if the email option is chosen then the attached PDF is incorrectly overwritten with the text of the email template.

Workaround

Either generate the PDF again later if needed, or refer to outbound copy of email in your email program (if using SMTP, CC or BCC yourself the emails for record keeping).

Linked Stock Items can allow negative stock situations if users click “No” to backorder prompt during supply of a sales order.

Issue ID: EXB-6714

When supplying a Sales Order, if a linked stock item is in use then negative stock quantity prompts will correctly raise a warning that the item will go into negative and that the order should go into Backorder.

However, clicking No on the backorder prompt allows the lines to be recorded as supplied and an invoice generated.

Workaround
Enforce process - users should always click Yes on backorder prompts during supply
OR

Use the actual stock item, not the linked stock item, to generate the sales orders.

Emailing a Debtor Invoice from the Sales Order Supply process doesn’t include Debtor CC Or BCC addresses

Issue ID: EXB-6722

The CC/BCC from Details 2 of debtor are currently not applied during Sales Order processes, which can lead Debtor Invoices sent without their CC/BCCs pulled from the debtor.

Workaround:

Send email directly from the Debtor screen > Transaction tab.

Emailing a Sales Order doesn’t include Debtor CC or BCC addresses

Issue ID: EXB-6722

Emailing a Sales Order doesn’t use Debtor CC or BCC addresses

Workaround
None available. Currently the feature doesn’t extend to Sales Orders.

SALESORD_LINESTATUSES stored procedure incorrectly sets orders to “HAS_UNSUPPLEID='N'“ when there are a mx of over-supplied and undersupplied lines.

Issue ID: EXB-6713

The SALESORD_LINESTATUSES stored procedure sums all lines against a sales order together regardless of stock item, to determine if the order has anything left to supply.

This is probably incorrect for most businesses, as it will allow the following situation:

Stockcode

Ordered

Supplied

STAPLER

1

2

RULER

1

0

To result in the order having it’s HAS_UNSUPPLIED flag set to No.

Workaround:

Modify the SALESORD_LINESTATUSES stored procedure to match required business logic for your business.

An example modified stored procedure is in the expand below.

Example of a reworked procedure, please ensure any changes you make have been t3ested to meet your business requirements.
SQL
CREATE PROCEDURE SALESORD_LINESTATUSES
  @ORDERNO INTEGER,
  @UNRELEASED  CHAR(1)  OUTPUT,
  @BACKORDERED CHAR(1)  OUTPUT,
  @UNSUPPLIED  CHAR(1)  OUTPUT,
  @UNINVOICED  CHAR(1)  OUTPUT,
  @UNPICKED    CHAR(1)  OUTPUT
AS
BEGIN
/*Example modfieid SALESORD_LINESTATUSES prodcedure
  Author: MYOB Support, Will Howard
  Date: 2025-01-16
  Purpose: make individual lines evaluated to determine status.
  All Lines individually evaluated: This version of procedure isn't able to compare the totals for a given stock item, which means if a stock item is listed twice, 1 line oversupplied, 1 line unsupplied, the order would show HAS_UNSUPPLIED.
  Stock quantities & Linked items: If editing this to be aware of stock quantities, you may also need to be aware of linked StockItems.
  Unprotected from float rounding: The version shown here isn't protected against floats, and could have strange results if floats are involved.  You may want to consider explciitly rounding the values before evaluating if they are 0.
*/
  SET @UNSUPPLIED  = 'N'
  SET @UNPICKED    = 'N'
  SET @UNINVOICED  = 'N'
  SET @UNRELEASED  = 'N'
  SET @BACKORDERED = 'N'
  SELECT @UNSUPPLIED = MAX(CASE WHEN  ((ORD_QUANT-CORRECTION_QUANT)-SUP_QUANT) <>0 THEN 'Y' ELSE 'N' END),
         @UNPICKED =  MAX(CASE WHEN  ((ORD_QUANT-CORRECTION_QUANT)-PICKED_QUANT)<>0 THEN 'Y' ELSE 'N' END),
         @UNINVOICED = MAX(CASE WHEN  ((ORD_QUANT-CORRECTION_QUANT)-INV_QUANT )<>0 THEN 'Y' ELSE 'N' END),
         @UNRELEASED = MAX(CASE WHEN  ((ORD_QUANT-CORRECTION_QUANT)-RELEASE_QUANT)<>0 THEN 'Y' ELSE 'N' END),
         @BACKORDERED = MAX(CASE WHEN  (BKORD_QUANT)<>0 THEN 'Y' ELSE 'N' END)
   FROM SALESORD_LINES
   WHERE HDR_SEQNO=@ORDERNO

   SELECT @UNRELEASED UNRELEASED,  @BACKORDERED BACKORDERED, @UNSUPPLIED UNSUPPLIED,
                           @UNINVOICED UNINVOICED, @UNPICKED UNPICKED

    END

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.