Not getting our update emails yet?
Stay informed about the latest product enhancements, new features, and bug fixes.
Sign up now.
Looking for release notes from other TecCom solutions?
Click here.
- #687933 Improved External Code handling for Customers in inbound and outbound messages.
- #684897 DesAdv volume fields are now converted from volume unit defined in Inventory and warehouse management parameters to the System unit of Dry volume class.
- #691582 Added new option in TecCom Parameters to skip Sales order confirmation posting during large order processing.
- #677184 Added new Data entity for TecCom Dispatch modes.
- #700306 Added Incoterm codes management and mapping. Now it allows configuring which Incoterm codes are allowed for customers and validates it when receiving inquiries and orders.
- #675430 Corrected an issue where Inventory Status was not considered when Availability inventory dimension was set to Item.
- #672991 External item number search was corrected to properly handle External item descriptions linked to Item – customer group.
- #672262 Fixed an issue which prevented usage of Units longer than 3 characters.
- #648753 PacketCount element in DesAdv 2.0 was corrected to always contain 1 for all packages except the first summary package.
- #614234 Sales line quantity is now always set to ConfirmedQuantity to support partial delivery scenario without backorder.
- #667794 Added Advanced warehouse availability setup, enabling inventory visibility in specified warehouses across companies.
- #672728 WHSContainerTypeV2 data entity was extended with TecCom Package Kind field.
- #648711 New option to include DeliveryParty in the header of consolidated invoice consisting of DesAdvs with the same DeliveryParty.
- #598754 Original sales line details are now used for OrderRef and OrderItemRef in TXML Invoice 2.5 in case of returns credit note. Link to the original sales line is based on InventTransIdReturn.
- #592460 Corrected Tax Percent in TXML Invoice 2.5 in case of tax exempt.
- #590512 Corrected zero tax percent in TXML Invoice 2.5 in case of zero taxable amount.
- #588517 Improved delivery date control during Sales order creation from TXML Order 4.1 message to address sales lead time issues.
- #587276 Percent value in AllowOrCharge element of TXML Invoice 2.5 is now always positive for better compliance with message guidelines.
- #581202 Improvements in TXML Invoice 2.5 Tax element export for better compatibility with GOLDA and business rules: TaxableAmount element is only exported in case of multiple tax rates or in the TaxTotals. Amount element is always exported for GOLDA customers, in TaxTotals or when there are multiple tax rates.
- #579892 Improved physical availability calculation accuracy by avoiding direct usage of InventSum table.
- #578627 Fixed divide by zero error occurring in invoices with zero customer balance.
- #577955 Refactored tax handling in TXML Invoice 2.5 to a more robust version supporting reverse charge and other special cases.
- #545639 Addressed issues with AllowOrCharge in TXML Invoice 2.5 credit note.
- #562313 Improved datetime parsing in OrderIssueDate to support TXML 4.1 Order messages converted from TXML 5.
- #576302 Removed Response element with ResponseClass="Error" Code="1004" from Inquiry response when items are not available.
- #576070 Response text informing about auto-charges is no longer provided in OrdRsp 4.1 message if the charge is internal (charge code posting is not related to customer), added support for multiple auto-charges per line in OrdRsp 4.1 Response text, corrected Response text for charges based on percentage or pcs.
- #600351 Added support for TXML Invoice 2.5 BuyerOrderNumber based on manually entered Customer requisition in Sales order / Return order header.
- #586293 New option was added to TecCom parameters to confirm delivery date only for physically reserved items in TXML OrdRsp 1.0.
- #582703 Added support for SSCC package numbering for TXML DesAdv 2.0.
- #547216 DesAdv message is no longer sent for packing slips posted from return orders.
- #548102 XML override adds default OrderProcessing and ItemProcessing attributes if missing in the order request.
- #548706 DeliveryInfo element is now provided in OrdRsp 1.0 messages related to large orders.
- #553198 Process pending messages batch job performance optimization (added missing index for status field).
- #554185 Fixed high-memory consumption and batch job failure in certain intercompany direct delivery DesAdv transactions.
- #547644 e-Invoicing web service URL is now configured separately from reverse messages on e-Invoicing tab of TecCom parameters.
Version 1.11.0.8 is the next version after 1.0.0.11.
Starting from version 1.11.0.8, a new version numbering logic was introduced:
| Position |
Example |
Role |
Meaning |
| 1 |
1 |
Major |
New features, breaking changes |
| 2 |
11 |
Minor |
New features, no breaking changes |
| 3 |
0 |
Patch |
Bugfixes, no breaking changes |
| 4 |
8 |
Build |
Continuous build / revision number |
- Missing delivery party in Invoice 2.5
- TXML Invoice 2.5 quantity element is changed from data type decimal to integer
- CountryOfOrigin has been corrected from 3 to 2 digit ISO code
- StatisticsGroup mapping is corrected to the Intrastat Commodity code (CustInvoiceTrans.IntrastatCommodity)
- Customer/account fields added to existing entities to improve import/export functionality
- Delivery party was missing in the Despatch Advise message. This has been added.
- Address deletion on D365 customer page should trigger deletion of the related TEC Address records instead of leaving the UI-invisible orphan record.
- Content of the DeliveryParty element in the outbound XML messages (OrdRsp but probably also others) was in certain scenarios incorrect. ID should match with the request and address with the Sales Order header.
- When "allow using duplicate order numbers" is set to NO, this was not allowing orders from other customers with same reference. Fix is narrowed down to customer level instead of environment level. With this fix each customer can use same reference once.
- Additional parties staging table index was extended to prevent duplicate errors on import
- Empty lines in DESADV message - Creating packing slip from the order instead of shipment results in empty lines in DESADV message. This has been fixed.
- Double lines in DESADV message – A second or additional order line that is added via separate work to an existing shipment with the original ordered qty results logically in 2 lines, nevertheless it mentions total quantity on both lines in DESADV. So 2 lines of 10 and 10 in the order results in DESADV in 2 lines with 20 and 20. This has been fixed.
- Orders received without BACKORDER setting in the header results in orders being processed only partially.
- Fixed an issue causing potential duplicate DesAdv lines on ITEM LIST when shipping from warehouse without enabled warehouse management process.
- Fixed a problem with potential duplicate lines in DesAdv packages when shipping from warehouse with enabled warehouse management process.
- Corrected a bug where DesAdv was exported as an ITEM LIST without package information, although warehouse had warehouse management process enabled. This happened when there was no warehouse information on the sales order / packing slip header.
- UnitPriceBasis is added as FreeText in Invoice 2.5 for Golda customers
- New entity added for Customer XML override settings. Besides import also export is possible.
- If Calendar is not set on warehouse or entity, scenario can happen that order is created without expected ship/receipt date. Safety net implemented: If at order creation no expected dates are set, use first possible date.
- Tax Element on the surcharges is always shown. Line Tax elements now include line-related allowances and charges.
- There is a separate Tax element for each tax used within line or related allowances or charges.
- Tax percentage is now zero in TXML for reverse charge.
- AllowOrCharge element Discount has been added to show discounts in TXML between Gross and net prices as allowance. If there is no discount, no discount allowance is exported. Total discounts from Trade agreements (percentage or fixed amount) are included in the line discount allowances.
- Customer requisition field is no longer populated by timestamp on Sales order or Return order creation. Timestamp is still added to the TXML BuyerOrderNumber element during export, if the Customer requisition field is empty.
- From the UnitPrice, TotalPrice, TotalValue and AdditionalPriceType Grossprice on the invoice, the TotalPrice and AdditionalPriceType GrossPrice has been reviewed and updated to reflect gross price information.
Note: Version 1.0.0.10 was not released and is replaced by 1.0.0.11.
- Delivery party was missing in the Despatch Advise message. This has been added.
- It is now possible to apply XML overrides to a specific order type only, using XPATH filters.
- Delivery dates issued by the customer that are not in line with D365 receipt or transport calendar, were blocked until version 1.0.0.8. If a customer is not in the position to send a valid delivery date, you as supplier, can set on customer level if you want to accept this order and how to process the (invalid) delivery dates initiated by the customer based on your order entry deadline:
- Option 1: requested delivery date was provided but is ignored by means of XML override > Next possible delivery date from today will be provided, according to the standard D365FO business logic
- Option 2: requested delivery date was provided and customer-level setting "Offer next possible delivery date" = "No" (default) > Check if the requested delivery date can be met, according to the standard D365FO business logic. Reject the order line if not.
- Option 3: requested delivery date was provided and customer-level setting "Offer next possible delivery date" = "Yes" (upon agreement with customer) > Check if the requested delivery date can be met, according to the standard D365FO business logic. If not, use the standard D365FO business logic to calculate the next possible delivery date after the customer requested delivery date.
- Consolidated DesAdv and Invoice messages are supported.
- Requested shipdate on orderheader was only showing order creation date. Date is now in line with manual order creation logic and calculated based on requested receipt date.
- TotalPrice element in creditnote's with surcharges was not reflecting correct value. This has been solved in case of credit note's.
- Messages created by batch job processing of sales confirmation, dispatch advise and invoice resulted in only 1 message of the first order number within the journal. In case of low batch frequency or large order volumes, a situation can occur that more orders can be part of a journal posting. The TecCom functionality is enriched to trigger a message for each unique order within the journal posted.
- Applying a delivery schedule on the order line resulted in lower prices every time the sales order confirmation was created. This has been solved and prices remain the same no matter delivery schedule is applied.
- GOLDA functionality compliant with 2023 guidelines (including Tax Exempt)
- Aktivbank functionality upgraded to support multi supplier/buyer requirement. Superfluous settings removed.
- For Large Order Processing we improved the process: First processing all lines before header is updated. With this sequence order completion batch job can only change orders that are fully created.
- Tax amount added to charges element in invoice XML
- The Additional party links - parent qualifier allows you to add 1 or more additional parties into the same XML segment.
- D365 TecCom security role added, which should be assigned to the service account. This new role will have only the role and privilege to perform necessary communication.
- TXML Invoice message function on customer level gives the flexibility to set per customer the invoice message function setting to Copy or Original
- From security point of view we recommend to change the current TecCom administrator role to TecCom service user role.
- Urgent fix in OrdRsp 1.0 message due to incorrect prices for all lines that come after an error/reject/exception order line. When issue occurred, prices from orderline C were set at items of orderline B in the OrdRsp 1.0 message.
- Dispatch mode "Stock order" from XML message was incorrectly mapped to dispatch mode "Normal" within D365 for processing. This mapping is corrected from Normal to Stock order within D365.
- Requested shipdate on orderheader was only showing order creation date. Date is now in line with manual order creation logic and calculated based on requested receipt date.
- TotalPrice element in creditnote's with surcharges was not reflecting correct value. This has been solved in case of credit note's.
- Any manual order created will get a default customer requisition value of yyyymmdd-hhmmss, which is based on time zone set on legal entity. This field can still be edited/changed by the order handler. Where needed a leading 0 is applied to achieve the hh notation.
- Orders will not be rejected in full anymore when a faulty sales order line is included. Despite one or more faulty order lines are received in an order from the TecCom Portal, the sales order will still be created in D365 with all correct order lines. All faulty order lines will be rejected in the order confirmation message towards the customer/TecCom portal.
- Supplier stock levels communicated on stock enquiries from the TecCom portal can now be narrowed down to 1 Inventory status eg. Available. If there is no inventory status selected, the full Available physical stock will be used for the response. The Available physical is currently the sum of all non-blocked inventory statuses deducted by any reservation.
- The invoice options on a TecCom customer has 2 options: None = No invoices will be sent to the TecCom customer if invoice setting is None on the buyer account. Version 2.5 = Invoice is sent to the TecCom customer if invoice setting is Version 2.5 on the buyer account.
- Retry logic has been put in place to avoid rejection of any TecCom orders. This scenario could happen in case 2 or more orders are entered at exactly the same time and try to obtain remaining stock of the same item. Number of retries and time between retries can be set at the Stock Order Error Handling.
- There are 2 stock availability calculation logic options to choose in the TecCom parameters: Physical -> Physical availability minus reservations = Available Physical. ATP -> Physical inventory conform D365 ATP logic, where physical reservations are not considered.
- "Allow using duplicate order numbers" functionality was not allowing duplicate order numbers. This has been fixed and can be set per TecCom customer.
- Resent original document functionality did not trigger the resending of selected document. New button "Teccom resend original" is made available for resending confirmations, dispatch advises and invoices. This button ignores electronic document settings.
- New button "Teccom resend original" is made available for resending sales confirmations, dispatch advises and invoices. This button ignores electronic document settings.
- Confirm date option did not stamp the calculated ship and receipt dates on the confirmed shipping or receipt date fields. This is working well as of this version.
- Message type for a credit note has changed from Invoice to CreditNote and amounts involved are set to an absolute value (no minus).
- Reverse Messages Web Service URL updated in this document.
- Large orders can be processed in a batch job, which will improve system performance. Large orders threshold can be set based on amount of sales order lines per order.
- Setting available in the TecCom Parameters which will allow to take the primary address from the buyer if delivery party ID is the same as buyer party ID. The delivery ID including delivery address will be ignored on the incoming order.
- Any manual order created will get a default customer requisition value of yyyymmdd-hhmmss. This field can be edited/changed by the order handler.
- Delivery schedule possible with TecCom sales orders.
- Confirm date option available for TecCom sales orders.