Skip to main content

Coresuite 8.40 - Changelog

Coresystems Development
Updated

Introduction

This article outlines the key changes introduced in Coresuite version 8.40, along with important instructions for upgrading - especially if you’re currently using version 8.35.


Important: Upgrading from Coresuite 8.35 to 8.40

In Coresuite 8.35, we introduced a change where company-specific add-on files are stored in either the %ProgramData% or %LocalAppData% folders, depending on how the software is installed.
For more details, see the Coresuite 8.35 Changelog.

During internal testing of Coresuite 8.40, we discovered a limitation during testing: the upgrade process does not always overwrite Coresuite files. This is due to a .NET Runtime behavior that causes SAP Business One to miss cleanup signals. Even if the add-on is removed via SAP’s Add-On Administration, the old company-specific folders may persist, leading to conflicts or outdated files.


Recommended Upgrade Steps

If upgrading from a version before 8.35:
You can upgrade directly to 8.40. The installer will handle the changes and no manual cleanup is required.

If upgrading from 8.35:
Option A:
Follow these steps to ensure a clean upgrade:

  1. Upgrade to Coresuite 8.40 via Add-On Administration in SAP Business One.
  2. Restart Coresuite to ensure the new installer is active.
  3. Remove Coresuite 8.40 via Add-On Administration in SAP Business One.
    - This triggers the correct removal signal for company-specific folders with the new installer.
  4. Restart SAP Business One.
  5. Install Coresuite 8.40 again to deploy files properly.

Option B:

  1. Stop Coresuite on all machines where it is running.

  2. Uninstall Coresuite 8.35 or upgrade Coresuite to version 8.40 using the Add-On Administration in SAP Business One.

  3. Manually delete any Coresuite-related folders named after company databases located in:

    • %ProgramData%

    • or %LocalAppData%
      (Location depends on the installation context.)

  4. Restart SAP Business One as usual.

Once Coresuite version 8.40 is installed, these additional manual steps will no longer be necessary. Coresuite 8.40 correctly handles the removal of company-specific add-on files. The change is introduced in the Coresuite installer.

 

Major changes

Coresuite Designer: ZUGFeRD Custom Mapping for Datasource Document_90

The latest release of Coresuite Designer 8.40 enhances flexibility in handling ZUGFeRD format mappings. This update introduces the SWA_LD_ZUGFERDMAP90 table for the Document_90 data source, extending the custom mapping capabilities first introduced in Coresuite 8.35.

Customers can now define their own User-Defined Fields (UDFs) using these mapping tables:

  • SWA_LD_ZUGFERDMAP – for Document_88
  • SWA_LD_ZUGFERDMAP90 – for Document_90

The mapping functionality for SWA_LD_ZUGFERDMAP90 works the same way as SWA_LD_ZUGFERDMAP, which was introduced in Coresuite 8.35. For more details on the original mapping approach, refer to the Coresuite 8.35 Changelog – Coresuite Designer: ZUGFeRD Custom Mapping.

The system will automatically determine which mapping table to use based on the selected data source, ensuring a seamless mapping experience. This enhancement provides greater control and customization for users working with ZUGFeRD-compliant documents.

 

Coresuite Designer: ZUGFeRD Custom Mapping for Units of Measures (UOM)

A new User-Defined Table (UDT), SWA_LD_ZUGFERDUOM (SWA_LD Zugferd UOM Map), has been added:

This table allows users to create a custom mapping between INV1.unitMsr in SAP Business One and the UnitCode in the TradeLineItem of the ZUGFeRD XML document.

How to Create a Mapping

1. Add a new line to the table and specify the mapping values.
2. The Code and Name columns must also be set.
3. Use the following naming convention for the Code and Name columns:
- The row number should be left-padded with zeros to a total of eight characters (e.g., 00000001).

Note: If no mapping exists, the system will default to H87 (piece).

For reference, at the end of this article, you will find the attached file UOM_Codes.xlsx, which contains a list of valid ZUGFeRD Unit Code values.

 

Coresuite Designer: Custom Mapping Between SAP Business One Tax Codes and ZUGFeRD Tax Categories

We've added a new mapping table SWA_LD_ZUGFERDTAX (SWA_LD Zugferd Tax Map), that allows you to define custom mappings between SAP Business One Tax Codes and ZUGFeRD Tax Categories.

  • The "S" (standard) tax category remains the default and does not require mapping.
  • You only need to map tax categories that differ from the default.

 

Coresuite Designer: PDF/A Generation on Sales AR - A/R Down Payment Invoice

Coresuite Designer now supports the generation of PDF/A documents for Sales A/R Down Payment invoices.

Previously, this feature was available for Sales AR Invoices and A/R Credit Memos. Expanding this capability ensures that credit memo documents meet the same archival and compliance standards as invoices, facilitating long-term digital preservation and improved alignment with regulatory requirements.

 

Coresuite Designer: Generate Different ZUGFeRD Versions for Different Customers

With Coresuite Designer 8.40, you can now generate different ZUGFeRD versions for different customers.

The default ZUGFeRD version for all generated documents can be configured in SAP Business One under:
Administration → Add-Ons → Coresuite Designer → Designer → Configuration.

On the "General" tab, we have added a new dropdown field called "ZUGFeRD Version", where you can select values:
 - Latest - Always use the latest available ZUGFeRD version, even when a new version is introduced in future Designer updates.
 - 230 - 2.3 - The latest version currently supported by the third-party ZUGFeRD library.
 - 200 - 2.0 - The first ZUGFeRD version available in the third-party library.


If you need to override this global setting for specific customers, you can do so in the Business Partner master data using the User Defined Field (UDF) "ZUGFeRD Version". This allows you to generate different ZUGFeRD versions based on individual customer requirements.

 

SwissPayment: Improved Exchange Rate Handling for Payment Calculations

We are introducing an enhancement to the Payment Wizard Swiss that gives you more control over how payment totals are calculated when exchange rates are involved.

In versions released after 2023 but before SwissPayment 8.40, the displayed totals were sometimes calculated incorrectly, particularly when:

- Future-dated exchange rates were defined, and
- The "Use Posting Date as Exchange Date" option was enabled in the SwissPayment configuration on the Payment wizard swiss tab.

A new configuration option, "Recalculate Saved Runs" has been added that allows the system to recalculate totals based on the current exchange rate when a saved payment is loaded.
- This option is disabled by default to maintain existing behavior.
- You can now enable it via a new checkbox in the SwissPayment configuration.

 

 

 

Related articles

Comments

0 comments

Article is closed for comments.