Release 21.02.01
Compatibility improvements
Included changes for DI behavior on drafts on SAP 10.
No visual or user behavior has changed.
Included changes for DI behavior on drafts on SAP 10.
No visual or user behavior has changed.
This release includes a new feature regarding the ShipEasy integration.
A new setting was added:
When the new setting is set to YES (checked)
If FreeShipping (U_TWBS_UPS_FreeShp) is NO, then the solution will add the U_TWBS_UPSExpense amount to the configured freight for ShipEasy, and add the Fixed Charge (if set in the Avatax Configuration).
Upgraded all component of the solution: Avatax Add-on, Avatax Event Service and Avatax webUI app to use the latest available Avatax REST API connector version (v20.12.1).
This let’s the SAP B1 solution components support the latest available functionalities and calculation responses returned from Avatax.
New functionalities were added to ShipEasy integration logic. This behavior applies when creating new documents using the Document Generation Wizard.
When Add ShipEasy Expense Amount as a Freight is enabled, the value setted in the base document header UDF U_TWBS_UPSExpense is copied to the target document, and set to the selected Freight for ShipEasy expense amount additional expense.
Performance improvements focused on external calculation mode on documents with several lines and draft documents.
A new customization is available to user a Sales Document Header field value, SAP native or UDF, as a Reference when sending the document to Avalara.
The value is sent in the Reference field of the Avalara transaction, and it’s visible from the Avalara web console.
If you intend to use this feature, you must check the box to enable it, and complete the marketing document field name you intend to use.
As requested by Avalara, the connector is updated to NOT send by default address geo coordinates: latitude and longitude in tax calculations.
This is due to the Streamlines Sales Tax (SST) functionalities implemented by Avalara, that require not including geo coordinates in regular tax calculations, and only request calculations using street level information.
It is now possible to use any of the Business Partner Master Data User Defined Field value as the Avalara Customer Code for tax transactions.
The field can be selected from the Avatax Settings:
Fixes were added for AR Cancellation Invoices when using the External Tax Mode.
The Document Generation Wizard now is capable to process draft documents and create “real” documents.
When selecting the new Draft Document checkbox as the base type, the base documents will be the same type as the target type, for example base draft AR Invoices to create Invoices.
Fix to set calculated tax rate to Line UDF when multiple lines with the same ItemCode are in the document. Only affecting to Line and AdditionalExpense tax mode.
Fix to recalculate tax on some draft documents. For ExternalTax calculation mode.