Module history for Sage X3

Version 16.2
e-InvoiceLink

Sage X3 fixes

Notes in this version: 6

All versions Public history — PDF

Version contents · 6

IBAN selection according to the Active Flows scope
Blocking check for IBAN presence
Preserving existing setup when applying the patch
Consistent environment for electronic addresses
Function compatibility with the batch server
Cockpit optimisation and reliability improvements

Fix1

IBAN selection according to the Active Flows scope

Issue

IBAN selection always gave priority to the site, then the company, without considering the level selected in Active Flows.

Impact

The bank details included in the invoice could fail to match the configured issuing scope.

Fix

The lookup now prioritises the company or site according to the Active Flows rule applicable to the invoice. The other level remains the fallback when the priority IBAN is missing.

Expected result

the IBAN included in the UBL file gives priority to the issuing scope defined in Active Flows, while retaining fallback between company and site.

Fix2

Blocking check for IBAN presence

Issue

A missing IBAN after searching the company and site was not blocked by a dedicated check before UBL generation.

Impact

Generation could continue without the expected issuer bank details.

Fix

A check now blocks generation and sending when no IBAN is available at either authorised level. The log identifies the relevant company and site so the setup can be completed.

Expected result

Without an IBAN on either the priority entity or the fallback entity, the invoice is neither generated as UBL nor transmitted.

Fix3

Preserving existing setup when applying the patch

Issue

Applying the patch could overwrite existing setup in miscellaneous tables 6380 and 6143.

Impact

Values used for flows could be replaced during the update.

Fix

Patch component assignment has been corrected to preserve the contents of these tables.

Expected result

applying patch v16.2 now preserves the existing setup in miscellaneous tables 6380 and 6143.

Fix4

Consistent environment for electronic addresses

Issue

The environment parameter could be incorrectly interpreted as Sandbox when it designated Production. An empty or invalid value could also be accepted as Sandbox.

Impact

Electronic address selection risked using a different environment from the one expected for the invoice.

Fix

Production and Sandbox values are now normalised and checked before address lookup. An invalid value or the absence of an active record in the correct environment blocks generation and sending. The message specifies the relevant environment.

Expected result

an invoice can be generated and transmitted only when the issuer's and customer's electronic addressing setup matches the environment defined in YB2E5ENV.

Fix5

Function compatibility with the batch server

Issue

The sales sending and purchase retrieval functions relied on interactive operation incompatible with batch server tasks.

Impact

Creating or executing a task could fail with the messages “Action not generated in this function” or “File Non-existent CHSTD”.

Fix

The YB2E5V and YB2E5A functions have been adapted for scheduled execution while retaining the criteria entered at submission. Batch processing no longer displays interactive dialogs. The absence of incoming invoices is treated as an informational result rather than an error; the connection secret is no longer displayed in the log.

Expected result

the YB2E5V and YB2E5A functions can now be associated with batch tasks, criteria are retained until execution, and the absence of incoming invoices no longer causes an error status.

Fix6

Cockpit optimisation and reliability improvements

Issue

The cockpit analysed all validated invoices from the last 120 days, including those for unconfigured companies or sites. After the grids were populated, only the first line could retain the expected colour.

Impact

Unnecessary reads slowed cockpit opening, and colouring did not correctly distinguish all lines.

Fix

Loading is limited to configured issuing sites and avoids repeating checks on invoices already tracked. Invoices with errors remain visible even if their setup has changed. Colours are applied after the grids have been fully displayed.

Expected result

the cockpit loads faster by limiting analysis to configured issuer scopes, while keeping existing documents visible and correctly colouring all lines.

Version 16.2e-InvoiceLink

IBAN selection according to the Active Flows scope

Issue

Impact

Fix

Expected result

Blocking check for IBAN presence

Issue

Impact

Fix

Expected result

Preserving existing setup when applying the patch

Issue

Impact

Fix

Expected result

Consistent environment for electronic addresses

Issue

Impact

Fix

Expected result

Function compatibility with the batch server

Issue

Impact

Fix

Expected result

Cockpit optimisation and reliability improvements

Issue

Impact

Fix

Expected result

No matching release notes.

Version 16.2
e-InvoiceLink