Coresuite 8.35 - Changelog

Introduction

We are pleased to announce the release of Coresuite version 8.35. Below is a brief overview of the key updates introduced in this version.

For a full list of changes and enhancements, please refer to our Release Notes.

Important: If you have not yet upgraded to Coresuite versions 7.90 through 8.20, please be aware that you will need to update the full Coresuite add-on due to significant changes and performance improvements introduced in version 7.90. This update is crucial to ensure compatibility with version 8.35 and future releases.

Important Notice: Coresuite Add-On Installation Folder Change

As we announced in Coresuite 8.30 - changelog, there are key changes to the Coresuite add-on installation process with Coresuite 8.35.
For more details about the change, please see the article Important Notice: Coresuite Add-On Installation Folder Change.

Coresuite Designer: ZUGFeRD Profile Change

The ZUGFeRD profile in Coresuite Designer has been upgraded from the "Basic" profile to the "Extended" profile. The "Basic" profile, used previously, supported only a limited subset of data fields available in SAP Business One, restricting the depth and accuracy of invoice data exchange.

With the "Extended" profile, a broader range of data fields in SAP Business One can now be utilized, ensuring more comprehensive information is included in electronic invoices. This update aligns with the ZUGFeRD 2.2 (and 2.3) standard and improves compatibility with partners and systems requiring richer invoice details. It also supports better automation of invoice processing and compliance with e-invoicing requirements in various industries.

This enhancement ensures that critical business data in SAP Business One is accurately reflected and shared, reducing manual corrections and streamlining your invoicing workflows.

Upgrade to ZUGFeRD 2.3

With this release, the generation of ZUGFeRD files is being upgraded from version 2.2 to version 2.3. This ensures compliance with the latest standards and improves compatibility with updated financial and invoicing regulations.
Additionally, to align with the ZUGFeRD 2.3 naming convention, the attached file name has been changed to "factur-x.xml".

Coresuite Designer: ZUGFeRD Custom Mapping

The latest release of Coresuite Designer 8.35 introduces a new feature that enhances flexibility in handling ZUGFeRD format mappings. This update includes the deployment of the SWA_LD_ZUGFERDMAP table, which allows customers to define their own custom UDFs (User-Defined Fields).

In earlier versions, a separate table (SWA_LD_ZUGFERDEXT22) was introduced specifically for ZUGFeRD version 2.2 mapping. However, with the new approach, the SWA_LD_ZUGFERDMAP table will serve all current and future ZUGFeRD versions, simplifying the structure and ensuring long-term maintainability.

If you installed the previous EarlyBird version 8.35 of Coresuite Designer on a production database, you must remove the old version before upgrading. This ensures compatibility with the latest improvements.

How to Remove the Old Table (SWA_LD_ZUGFERDEXT22)

To prepare your system for the new version, follow these steps:

1. Remove the Old Designer 8.35 Version

   • Use the CAA Tool to remove the existing Coresuite Designer 8.35 Release Candidate from your database.

2. Delete the Old Mapping Table

   • In SAP Business One, navigate to:
     Tools → Customization Tools → User-Defined Tables - Setup...
   • Scroll down and find the table: SWA_LD_ZUGFERDEXT22
   • Right-click → Remove → Update

3. Install the New Coresuite Designer 8.35

   • Once the old version and table are removed, proceed with installing the new Coresuite Designer version.

How Mapping Works:

Coresuite Designer retrieves data using the B1_Data datasource, which is used to populate the ZUGFeRD XML file. The mapping between B1_Data elements and the XML structure is stored in the @SWA_LD_ZUGFERDMAP table.

To allow for greater customization, two new fields have been introduced:

• Datasource Override – Allows specifying a different datasource than the default one in the "Datasource" column.
• Field Override – Enables specifying a different field than the default one in the "Field" column.

Important: If overriding either the datasource or field, both "Datasource Override" and "Field Override" must be set to ensure proper functionality.

For each XML element, the "Datasource Override" and "Field Override" values must exist in the B1_Data datasource within the Designer layout.

Warning: Only the "Datasource Override" and "Field Override" columns should be modified. All other columns are system-managed and may be updated automatically during Coresuite Designer upgrades. Changing system columns could lead to unexpected behavior.

Example Use Case

If you need to replace Document.DocNum with a user-defined field (U_SampleUDF), you can set:

• Datasource Override → "Document"
• Field Override → "U_SampleUDF"

Considerations for Datasource Changes

If overriding the default datasource, ensure you do not mix header and row tables. Headers typically contain a single row, whereas row tables can have multiple entries, making it difficult to determine the correct line. For row datasources, the Datasource Override should always match the default datasource.

Coresuite Designer: PDF/A Generation on Sales AR - Credit Memos

Coresuite Designer now supports the generation of PDF/A documents for Sales AR Credit Memos.

Previously, this feature was available only for Sales AR Invoices. 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 Service: Enhancement for IDP Support in SAP Business One

Coresuite Service now supports Identity Provider (IDP) functionality for SAP Business One, allowing better integration in environments where users access the system using domain-based accounts.

A new optional attribute, clouduser, can be added to the CoresuiteServiceConfig.xml file located in C:\ProgramData\Coresystems\Coresuite Service. This is necessary in cases where domain accounts are used to log in to SAP Business One. If your system uses such accounts, ensure the following settings are configured:

- user: The SAP Business One user, e.g., "manager".
- clouduser: The corresponding domain account in the format "DOMAIN\user".

For environments that do not use domain-based logins, this attribute is not required, and the existing configuration will remain functional.

This update improves compatibility with hybrid and cloud setups, streamlining user authentication and access management.

SwissPayment: Name Change of the Payment File

The naming convention for payment files generated by SwissPayment has been updated. Starting with this release, the file names follow the format <BillerID>_<TransactionID>.XML.

This adjustment aligns with the standards defined by the SIX Group, ensuring compatibility and compliance with their latest requirements for payment processing. The updated naming format facilitates better organization and traceability of payment files, streamlining payment workflows and improving integration with financial institutions.

SwissPayment: Bank Charges Determination Logic

With this update, when the "Use BP bank charges" option is selected in the SwissPayment configuration, the system will now output the bank charges exactly as set on the Business Partner (BP). The four valid bank charge types - SHAR, DEBT, CRED, and SLEV - will be fully supported.

Previously, while these bank charge types were recognized, they were only applied to cross-border, non-SEPA payments. This enhancement ensures greater consistency and alignment with BP-defined settings across all relevant transactions.