Update 27.1.202548.149437

Prev Next

Release Date: 28. November 2025

Release Summary

  • Resolved multiple issues in Business Central related to intercompany transactions and purchase invoice recalculations.

  • Key fixes include preventing AA0139 warnings by extending the "SCB External Document No." field length and ensuring receipt numbers are not randomly assigned.

  • Enhancements improve data integrity, prevent posting errors, and enforce consistent validation across batch processes.


Bug Fixes

General

AA0139 warning // The length of the string is 22, but is must be less than or equal to 20 characters

Resolved an issue where the "SCB External Document No." field in the "IC Outbox Transaction" and "Handled IC Outbox Trans." tables could exceed the allowed character length, resulting in an AA0139 warning and potential data truncation errors. The field length has now been updated to Code[35] to ensure compatibility and prevent overflow errors.

Technical Details:

  • Updated the field length for "SCB External Document No." to Code[35] in the relevant table extensions.

  • This change addresses the AA0139 warning and ensures that longer document numbers are handled correctly.

  • The update is compliant with the latest Business Central standards and prevents assignment overflow issues.

Impact:

  • Users will no longer encounter errors when document numbers exceed 20 characters in intercompany transactions.

  • No workaround is required; the issue is resolved in this release.

Recalculate Receipt… & Receipt Line Nos.

When using the “Recalculate Receipt…& Receipt Line Nos.” button on a purchase invoice that is not connected to any receipts, the system would insert a random receipt number from the system into the purchase invoice line (item lines only). This incorrect receipt number could not be removed or reset, resulting in posting errors and making it impossible to clear the field.

The system has been updated to ensure that the Receipt No. and Receipt Line No. fields are not set in the Purchase Invoice if there is no associated purchase receipt. This prevents random or unrelated receipt numbers from being inserted when recalculating on unconnected purchase invoices.

How to Reproduce (Before Fix)

  • Create a Sales Invoice in IC INVENTORY for an Intercompany Customer with an item line and post the invoice.

  • The corresponding Purchase Invoice is auto-generated in IC SALES with no receipt number entered.

  • Clicking “Recalculate Receipt…& Receipt Line Nos.” would insert a random receipt number unrelated to the invoice.

  • The field could not be cleared, causing posting errors.

Result (After Fix)

  • The “Recalculate Receipt…& Receipt Line Nos.” button will no longer insert a receipt number if the purchase invoice is not connected to any receipts.

  • The field remains blank unless a valid connection exists, preventing posting errors and user lock-in.

No error lock when posting Intercompany sales order in SALES with no buy-from vendor on the sales header

When posting a sales order from the SALES company with an IC buy-from vendor specified only on the sales line (not on the header), the system correctly locks the order and displays an error, indicating that posting must be done from the SUPPLY company. However, when posting multiple sales orders at once with IC buy-from vendor on the lines (but not on the header), the system allowed the orders to be posted without any error, leaving the corresponding orders stuck in the flow.

Batch posting of intercompany sales orders is now prevented when the buy-from vendor is not set on the sales header. The system now enforces the same error lock for multiple orders as it does for single orders, ensuring that orders remain locked in SALES and cannot be posted incorrectly.

How to Reproduce (Before Fix)

  • In IC SALES, create sales orders with no buy-from vendor on the header, but with IC buy-from vendor on the line.

  • Posting a single order correctly triggers an error and locks the order.

  • Posting multiple such orders at once would previously allow them to be posted, leaving the corresponding orders stuck.

Result (After Fix)

  • The system now blocks batch posting of such orders, ensuring consistent behavior and preventing orders from being left in an inconsistent state.

  • It is no longer possible to post multiple orders in the sales company under these conditions.