Coresuite 8.45 - Changelog

Introduction

We are pleased to announce the release of Coresuite version 8.45. 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.

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.

ZUGFeRD Implementation

For more details about the whole ZUGFeRD implementation in Coresuite-related products, please see the article Implementation of ZUGFeRD in Coresuite Designer.

Major Changes Delivered in Coresuite 8.45

Coresuite Installer: "SBO Fast Close on Exit" Delay

In Coresuite 8.20, the feature “SBO Fast Close on Exit” was introduced. When enabled, the SAP Business One client process is terminated once Coresuite is closed. This was designed to handle cases where the SAP Business One client would remain active after an add-on was started. For further details, see the Coresuite 8.20 - Changelog.

A drawback of this implementation was that changes made to forms were not saved before the client was terminated. To address this, Coresuite 8.45 introduces a configurable delay for the termination of the SAP Business One process. The delay is defined in seconds and gives the system time to save form changes before shutdown. The appropriate value depends on the specific environment, and we recommend starting with a delay of three seconds.

By default, the value is set to zero, which preserves the behavior from versions prior to Coresuite 8.45. 

The configuration can be found under Coresuite Administration → Global module configuration → Advanced Settings when the "SBO Fast Close on Exit" option is active. 

Coresuite Designer: PDFs From Designer in SAP Business One WebClient

The Coresuite Designer WebExtension is an add-on specifically designed for the SAP Business One WebClient. It combines the proven background technology from the standard SAP Business One client with the modern front-end framework of the WebClient.

Our solution for generating PDF layouts created in Coresuite Designer is based on the Coresuite Service. This service acts as a REST API server that processes requests from the SAP Business One WebClient, allowing the same layouts known from the standard fat client to be used for PDF output in the browser environment.

For more details about the functionality, please take a look at the article Coresuite Designer WebExtension Configuration and Deployment Guide.

Coresuite Designer: Enhancement of ZUGFeRD Mapping Tables

We added a new column "Hide" to the existing mapping UDTs SWA_LD_ZUGFERDMAP and SWA_LD_ZUGFERDMAP90 

• Hide - When set to “Y”, the specific field will not be output to the ZUGFeRD XML file.

Coresuite Designer: New ZUGFeRD Configuration Table

The newly delivered configuration table SWA_LD_ZUGFERDSET - SWA_LD Zugferd Settings allows you to control specific behaviors of the ZUGFeRD implementation.

Omit Specific Lines from ZUGFeRD XML file:
If you want to omit specific lines from the generated XML file, the following keys have been added:

• HideLineUDF: Specifies the line-level UDF used to determine whether a document line should be hidden.

• HideLineValue: Defines the UDF value (for the field specified in HideLineUDF) that indicates the line should be omitted.

The configuration above means that when the UDF “HideLineValue” on document rows contain the value “Y”, the rows will not be included in the ZUGFeRD xml file.

Exclude Negative Discounts from XML File:

• IgnoreNegativeLineDiscounts: When set to “Y”, negative line discounts will not be included in the output.

Coresuite Designer: ZUGFeRD - BT-132 / BT-X-21 - BuyerOrderReferencedDocument

Properties BuyerOrderReferencedDocumentLineId (BT-132) and BuyerOrderReferencedDocumentIssuerAssignedId (BT-X-21) have been added to the mapping table ZUGFERDMAP and SWA_LD_ZUGFERDMAP90.
 - When the UDF U_NameOfUDF (from U_DatasourceO=Row, U_FieldO) contains data, it populates BuyerOrderReferencedDocument (BT-132) or BuyerOrderReferencedDocumentIssuerAssignedId (BT-X-21) accordingly.
- By default, these properties do nothing. They must be overridden in the mapping table to take effect.

Coresuite Designer: ZUGFeRD - BT-10 & BT-13 - NumAtCard - Buyer Reference/Leitweg ID and Purchase Order Reference

BT-10 - BuyerReference
BT-10 will be set based on the Leitweg Id defined on the Business Partner. This value is user-defined in the mapping table under the key Header.BPLeitwegId, and is typically stored as a UDF on the Business Partner master data.

Solution:
• The system will first attempt to use the Leitweg Id (as per the mapping table).
• If the Leitweg Id is not defined, NumAtCard will be used.
• If both Leitweg Id and NumAtCard are defined, Leitweg Id will take priority.
• If you prefer to use NumAtCard regardless, this behavior can be customized within the mapping table. Please see the section V Mapping Tables - 1. User Defined Fields.

BT-13 - Purchase Order Reference
By default, the NumAtCard value will be used. Partners can override this field by specifying a UDF or custom value in the mapping table.

BT-10 and BT-13 are separate properties to respect their distinct purposes in the X-invoice.

Overriding via the mapping table remains fully supported, so partners can map custom UDFs to either field without changing the default behavior.

Coresuite Designer: ZUGFeRD - BT-132 / BT-X-21 - BuyerOrderReferencedDocument

Properties BuyerOrderReferencedDocumentLineId (BT-132) and BuyerOrderReferencedDocumentIssuerAssignedId (BT-X-21) have been added to the mapping table ZUGFERDMAP and SWA_LD_ZUGFERDMAP90.
 - When the UDF U_NameOfUDF (from U_DatasourceO=Row, U_FieldO) contains data, it populates BuyerOrderReferencedDocument (BT-132) or BuyerOrderReferencedDocumentIssuerAssignedId (BT-X-21) accordingly.
- By default, these properties do nothing. They must be overridden in the mapping table to take effect.

Coresuite Designer: ZUGFeRD - Determination of Bill To/Ship To Addresses

The Bill To/Ship To addresses included in the ZUGFeRD XML are determined based on the document-level addresses first, with a fallback to the Business Partner master data if necessary.

This logic ensures that the XML reflects the most specific and complete address available, while maintaining consistency with the Business Partner master data when document-level information is incomplete.

Bill To Address:
• If the document’s Bill To address contains a postcode, this address is used.
• If the document’s Bill To address does not contain a postcode, the Business Partner’s master data address is used instead. 

Ship To Address:
• If the document’s Ship To address contains a postcode, this address is used.
• If the document’s Ship To address does not contain a postcode, the Business Partner’s master data address is used instead.

Coresuite Designer: ZUGFeRD - BT-84 - ActualDeliverySupplyChainEvent - Service Date Determination

The Service Delivery Date is determined based on the following priorities:
Priority 1: Use ShipDate from the delivery note if the invoice is based on a delivery note
Priority 2: Use DocDueDate from the delivery note if the invoice is based on a delivery note
Priority 3: Use ActDelDate from the invoice if the invoice is not based on a delivery note
Priority 4: Use DocDueDate from the invoice if the invoice is not based on a delivery note

Coresuite Designer: ZUGFeRD - BT-73 - IBAN Determination

When no payment term is defined on the document, the system now automatically uses the house bank account defined on the Business Partner to determine the IBAN.
This ensures correct IBAN selection and consistent payment information generation, even when payment terms are not explicitly set at the document level.

Coresuite Designer: HTML Statement Support for Coresuite Service With Office 365

HTML statements now work when using Send Mode 12 (Coresuite Service with Office 365).

Important when using Send Mode 12 with HTML and Report Subscription:

1. Uncheck Auto Newline in Body from the Designer's configuration, as it interferes with HTML markup.

2. Define the list of documents to send in the SQL query in Step 3 (Parameters) of Report Subscription. Example:

   SELECT TOP 5
       DocNum,
       DocEntry,
       '9' AS LangCode
   FROM OINV
   ORDER BY DocEntry DESC

3. When sending e-mail, do not insert the template in the E-mail text field in Step 4. Instead:
   - Use Advanced Settings.
   - Fill in the related Printdefinition in its E-mail text field.
   - Make sure the HTML (Mode 0, 3, 4) checkbox is checked.
4. Replace the O@@RDR designations in the SQL statement and only use the parameters defined in Step 3.

SwissPayment: Instant Payments in SwissPayment

Support for Instant Payments has been added to SwissPayment for SAP Business One.

Changes:

• New UDF “Instant Payment” (Y/N) on marketing documents (used as default in Payment Wizard).
• New UDF “Instant Payment” (Y/N) on payments (internal use).
• New “Instant Payment” checkbox in the Payment Wizard grid.

Rules:

Marking a payment as “Instant Payment” in the wizard expresses intent. Actual processing as instant requires:

1. Payee IBAN is a valid QR-IBAN in Switzerland or Liechtenstein.
2. Payment currency is CHF.

If these conditions are not met, the payment is processed as a standard payment.

File Generation:

• Instant Payments are included in the pain.001 payment file.
• They are mapped as Payment Type D according to the Swiss standard.

Coresuite Time: Reset EMME functionality improvement to work with serials and batches

In Coresuite Time 7.95, we delivered a feature called “Reset EMME”. This feature returns the materials/items from canceled/credited invoices so they can be used again. 

The feature appears as ‘Reset EMME’ when you right-click on canceled invoices or credit notes.

This functionality must be used directly on the original canceled document in order to make the EMMEs available again.
 
With Coresuite Time 8.45, this feature is further improved to also reset used Serials and Batches.