Type = Technical Guides, Technical Tools, What's New,; Topic = Multienterprise Information Network Tower (MINT), Technical Documentation,;Persona = Solution Designer, TraceLink Administrator, User, Orchestration Architect, Solution Partner, Technology Partner,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = IT, Quality, Procurement,

What's new in the user interface

Explore what's new in the Multienterprise Information Network Tower, solution version 16.0.0 release. To learn more about the Multienterprise Process Link, version 2025.4.0 app that powers the solution, see What's new in the APIs.

Release information

This document describes the TraceLink capabilities included in the Multienterprise Information Network Tower, solution version 16.0.0 release, which is available on Validation on 11 Dec 2025 and Production on 10 Jan 2026.

The following solutions are impacted by this release and will be updated to the version listed:

• Multienterprise Information Network Tower, solution version 16.0.0

  Apps that support this solution version:

  • Multienterprise Process Link, version 2025.4.0

The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).

Download the PDF

Revisions

Date	Revision	Description
27 Nov 2025	01	Initial version.
11 Dec 2025	02	The following updates have been made since the previous revision was distributed: 13 issues are added to Resolved issues. 0 issues are added to Known issues.
10 Jan 2026	03	The following update have been made since the previous revision was distributed: The Production release date is updated from 03 Jan 2026 to 10 Jan 2026 for Production Frankfurt in Release information section.

Features

Multienterprise Information Network Tower, solution version 16.0.0

The following new or updated functionality is included in this release.

Send and Receive Handling Movement Instructions in the Web UI

Companies that own Multienterprise Information Network Tower can send and receive Handling Movement Instructions in the Web UI. Handling Movement Instructions allow manufacturers, brand owners, and logistics providers to send standardized instructions, such as transferring, blocking, releasing, or scrapping inventory to warehouses, distribution centers, or third-party logistics providers (3PLs). Standardizing these instructions reduces manual processing, ensures consistent execution, and supports compliance with internal quality policies and external regulations.

In the Web UI, Owners and Partners can:

• Create new Handling Movement Instructions

• Save drafts for later submission

• Edit line items (e.g. shipment preparation, marking and labeling, movement between warehouses)

• Search for and view instruction details

• Troubleshoot and resubmit instructions as needed

For companies whose Partners do not own Multienterprise Information Network Tower, Owners can add their Partner's users to their network and assign them the appropriate roles to enable them to create, draft, submit, search for, and view handling movement instructions in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Handling Movement Instructions are available in the logistics orchestration.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners.

Send and Receive Ocean Shipment Booking Requests in the Web UI

Companies that own Multienterprise Information Network Tower can send and receive Ocean Shipment Booking Requests in the Web UI. Ocean shipment booking requests allow shippers or logistics providers to send a booking request to a carrier or freight forwarder to reserve transportation space for their cargo specifying the desired routing, ports, container type, and shipment details who evaluate the request based on available capacity, routes, and schedules. It serves as the digital equivalent of a booking form, allowing shippers and their logistics partners to request vessel or transport space for upcoming shipments.

In the Web UI, Owners and Partners can:

• Create and submit ocean shipment booking requests

• Save drafts for later submission

• Edit line items, including cargo details, transport mode, schedule, and special handling or equipment needs

• Search for and view request details

• Troubleshoot and resubmit requests if needed

For companies whose Partners do not own Multienterprise Information Network Tower, Owners can add their Partner's users to their network and assign them the appropriate roles to enable them to create, draft, submit, search for, and view ocean shipment booking requests in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Ocean Shipment Booking Requests are available in the transportation orchestration.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners

Send and Receive Ocean Shipment Booking Confirmations in the Web UI

Companies that own Multienterprise Information Network Tower and their Partners can send and receive Ocean Shipment Booking Confirmations in the Web UI. Ocean shipment booking confirmations are created and sent by carriers, or freight forwarders after reviewing a booking request, submitted by shippers or logistics service providers (LSPs). The confirmation is received by the shipper or logistics service providers (LSPs) to verify whether their requested booking has been accepted, modified, or rejected.

In the Web UI, Owners and Partners can:

• Create and submit ocean shipment booking confirmations

• Save drafts for later submission

• Edit line items such as booking status, reference numbers, schedule details, container and equipment assignments, routing, transport mode, and explanatory notes

• Search for and view confirmation details

• Troubleshoot and resubmit confirmations as needed

For companies whose Partners do not own Multienterprise Information Network Tower, Owners can add their Partner's users to their network and assign them the appropriate roles to enable them to create, draft, submit, search for, and view ocean shipment booking confirmations in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Ocean Shipment Booking Confirmations are now available in the transportation orchestration.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners

Send and Receive Shipping Instructions in the Web UI

Companies that own Multienterprise Information Network Tower and their Partners can send and receive Shipping Instructions in the Web UI. Shipping Instructions are created and transmitted by shippers such as manufacturers, distributors, or third-party logistics providers (3PLs) to the carriers, freight forwarders, or other transportation partners responsible for physically moving goods to their destination. The Shipping Instruction transaction is a critical pre-shipment tool that ensures accurate, timely, and compliant execution, supporting efficiency, cost control, and a reliable end-to-end shipping experience.

In the Web UI, Owners and Partners can:

• Create and submit shipping instructions

• Save drafts for later submission

• Edit line items, including pickup and delivery locations, routing, transport modes, handling requirements, and special shipping conditions

• Search for and view instruction details

• Troubleshoot and resubmit instructions as needed

For companies whose Partners do not own Multienterprise Information Network Tower, Owners can add their Partner's users to their network and assign them the appropriate roles to enable them to create, draft, submit, search for, and view shipping instructions in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Shipping Instructions are now available in the transportation orchestration.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners

Support for Exporting Business Transaction Data

Multienterprise Information Network Tower Owners and their Partners can export filtered business transaction data to a CSV file in Base Transaction Object and Serialization Traceability Object screens enabling structured access to transaction details such as metadata, status, and any associated error messages. This functionality supports both senders and receivers of business transactions by providing a reliable way to review exchanged data outside the system.

The export feature enables users to generate structured records of exchanged data for troubleshooting and validation. By configuring filters such as transaction name, transaction ID, status, sender, and date range, users can extract only the data needed for their specific use case.

This functionality helps validate that transaction data aligns with internal systems, identify failed or incomplete transactions, and support compliance and audit requirements. Exported data improves operational visibility, enhances data integrity, and streamlines issue resolution. It also reduces reliance on manual checks, supports efficient reconciliation, and increases confidence in data accuracy.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners

Introduction of MINT Dashboards: TraceLink's Next Generation Data Visualization

This release introduces MINT Dashboards, which provides new insights into the data in a company’s licensed TraceLink products. MINT Dashboards gives users real-time visibility into their company’s data, based on the business objects (e.g. Purchase Orders) that are relevant to their company's use cases. Companies can create their own reports and dashboards (which can include a combination of tables and charts) to give stakeholders and decision makers easy access to the data that is most important to them. Displaying only the data that is relevant to the company’s business goals makes it easier to make quick decisions using the right data. This enhancement supports both existing and future transactions, giving each orchestration baseline visibility and access to scalable, actionable analytics. Users with the appropriate roles can view the dashboards linked to the MINT solution. For detailed information about Multienterprise Information Network Tower dashboards and the reports available, see View dashboards.

This feature also includes additional base and joint reports for External Manufacturing, Logistics, Commerce, and Transportation orchestrations.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners

Stabilization and Usability Enhancements

The Inventory Balance transaction has been enhanced to support responses to Handling Movement Instructions transactions. These updates enable MINT to accurately generate and respond to handling movement instructions messages with full support for new status codes and extended canonical mapping, improving interoperability and data consistency across ERP and TraceLink systems.

• Added mapping support for the STS segment from the new canonical segment to align with handling movement instructions response requirements.

• Enhanced canonical schema object canonicalInventoryBalance with new and updated type definitions and attributes.

The Carrier Shipment Status canonical has been enhanced to close a gap identified in return shipment and IoT data handling. These updates improve the accuracy and visibility of return shipment tracking by capturing detailed return destination, contact, and IoT device information at both the header and line levels. The enhancements deliver stronger end-to-end traceability and operational transparency, particularly benefiting logistics partners managing complex return and carrier status processes.

• Added returnToBusinessInformation fields at both the Header and Line levels to capture detailed return destination and contact information.

• Introduced new IoT-related fields to support better integration with connected device and service tracking.

An initial gap analysis was completed across multiple transaction types, including 812 (Credit/Debit Adjustment), 844 (Product Transfer Account Adjustment), 810 (Invoice), 849, 850 (Purchase Order), and 856 (Advance Ship Notice). These updates establish a clear framework for improving data consistency, schema accuracy, and transaction interoperability across all supported EDI message types.

• Schema Enhancements Identified: Several canonical schema updates were identified for key segments (N1, N2, CDD01, LIN02, N9, DTM01), along with field-level adjustments to align each transaction type with integration standards and business requirements.

• Data Quality and Structural Issues: The gap analysis found missing mandatory fields (e.g., N103/N104 in 850) and data inconsistencies, especially in the 844 transaction, which did not match published specifications.

• Transaction Validation Results: 810 and 856 transactions translated successfully without changes, while 812 transactions required canonical schema and transform updates for proper processing and interoperability.

This feature also includes other minor updates to improve the Multienterprise Information Network Tower solution's stability and its ability to communicate with other TraceLink apps and solutions.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments for both Owners and Partners.

Resolved issues

Multienterprise Information Network Tower, solution version 16.0.0

The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.

ID	Interface	Issue Description
CMCP-40483: Validation Failure in Order Shipment Status Due to Incorrect Mapping Logic	Web UI	Order Shipment Status transactions were failing during processing due to incorrect validation checks in the inbound JSLT mapping logic. As a result, valid shipment status messages were being rejected, preventing updates from being processed as expected. The inbound system maps are updated to apply the correct validation logic. Order Shipment Status messages now pass validation successfully and are processed without errors. This issue has been resolved.
CMCP-40488: Ocean Shipment Arrival Failure Due to Missing Enumeration	Web UI	Ocean Shipment Arrival transactions were failing during processing because the "vesselCodeType" picklist was missing the required USCENSUS enumeration value. This caused validation errors when transactions included this code, preventing successful submission or processing of arrival messages. The "vesselCodeType" subtype picklist was updated to include the missing USCENSUS enumeration value. Ocean Shipment Arrival transactions using this value now process successfully without validation errors. This issue has been resolved.
CMCP-40521: PO Creation Failure via UI Due to Outbound B2B Error	Web UI	Purchase Orders (POs) created from the UI were failing during outbound processing due to an error in the mapping logic. Specifically, the lineItemQuantityValue field was not being mapped to the canonical structure, resulting in an outbound B2B mapping error that prevented successful transmission. The system outbound maps were updated to correctly populate the "lineItemQuantityValue" field. As a result, POs created from the UI are now processed successfully in the outbound flow without errors. This issue has been resolved.
CMCP-40666: WSA Transaction Failures Caused by Shipped Date Field Handling	Web UI	WSA (Warehouse Shipment Acknowledgment) transactions were failing during processing when the ext_TRACELINK_shippedDate field was populated. The outbound JSLT maps did not include logic to handle this custom date field, resulting in mapping errors that prevented successful processing of the transaction. The outbound system maps are updated to include support for the "data.ext_TRACELINK_shippedDate" field. Additional logic was added to convert and map the field correctly, ensuring that WSA transactions with this field are now processed successfully. This issue has been resolved.
CMCP-40689: Inventory Update Failures Caused by Missing Value in Picklist	Web UI	Inventory Update transactions containing "inventoryStatusUpdateReasonCode": "SKUTRANSFER" were failing during validation. The failure occurred because the "SKUTRANSFER" value was not defined in the corresponding subtype picklist, causing the system to reject the transaction. The "inventoryStatusUpdateReasonCode" picklist for the Inventory Update subtype was updated to include the "SKUTRANSFER" value. Transactions using this reason code now validate successfully and are processed without errors. This issue has been resolved.
CMCP-40732: Purchase Order View/Edit Page Unavailable for Third-Party Logistics Providers	Web UI	In the catalogue solution, the View/Edit page named "Provider_thirdPartyLogisticsReceivedPurchaseOrder_View_Page" was missing from the packed assets downloaded from S3. As a result, MINT returned an error when users attempted to view or edit third-party logistics Purchase Order transactions, blocking access to the transaction details. The missing View/Edit page was added to the packed assets for the catalogue solution. Users can now successfully access and interact with third-party logistics Purchase Orders without encountering errors. This issue has been resolved.
CMCP-40788: Missing Unit of Measure in Logistics Purchase Order Transactions	Web UI	In Logistics Purchase Order transactions, the Unit of Measure (UOM) field was not being populated in the outbound message. This resulted in incomplete transaction data, potentially affecting downstream processing or integration with partner systems that require UOM for quantity-based operations. The system outbound mapping logic was updated to correctly populate the Unit of Measure field in the Logistics Purchase Order transactions. This issue has been resolved.
CMCP-40807: Incorrect Error Messages Caused by Missing Authorization Policy	Web UI	In certain failure scenarios within MINT, users were receiving incorrect or unclear error messages. This occurred because a required authorization (AUTHZ) policy was missing. As a result, when an unknown failure happened, the system could not correctly determine or display the nature of the issue, making troubleshooting more difficult. The missing AUTHZ policy was added to the MINT configuration. This ensures that, in the event of unknown failures, the system now returns accurate and informative error messages, improving clarity and user experience during error handling. This issue has been resolved.
CMCP-40872: ASN Fails to Map All Values in Array	Web UI	In Advance Ship Notice (ASN) transactions, only the first value in the productCodesIdentifiers array was being mapped. As a result, additional product identifiers, such as GTIN, NDC, or Internal Material Number were omitted from the outbound message. This led to incomplete product data and potential mismatches in downstream systems expecting multiple product identifiers. The mapping logic for ASN transactions was updated to support all entries in the productCodesIdentifiers array. All relevant product identifiers are now correctly included in the outbound message, ensuring complete and accurate product information. This issue has been resolved.
CMCP-40971: Issue Causing Inbound Invoices to Remain Stuck in 'Received Only' Status	Web UI	Some inbound invoice transactions were getting stuck in the Received Only status and not progressing through the expected processing workflow. This prevented the invoices from being fully processed and integrated into downstream systems, causing delays in financial reconciliation and related operations. System logic was updated to address the root cause preventing status progression. Inbound invoices now transition correctly beyond the Received Only status and continue through the complete processing lifecycle as expected. This issue has been resolved.
CMCP-40988: Product Transfer Account Adjustment Failure Due to Missing Enumeration	Web UI	Product Transfer Account Adjustment requests were failing during processing because the value "MUTUALLY_DEFINED" was not included in the list of valid enumerations for a required field. As a result, any transactions using this value were rejected, preventing successful submission and processing. The list of valid enumeration values was updated to include MUTUALLY_DEFINED. Product Transfer Account Adjustment requests using this value now pass validation and are processed successfully. This issue has been resolved.
CMCP-41000: Missing Support for Movement Types 503 and 504 in Canonical and IDoc Maps	Web UI	Inventory Update transactions using movement types 503 and 504 were not supported in the existing model and IDoc inbound and outbound maps. As a result, transactions with these movement types failed to process correctly or were excluded from integration flows, leading to incomplete inventory updates between systems. The Inventory Update model and both inbound and outbound IDoc mappings are updated to support movement types 503 and 504. These movement types are now correctly captured, processed, and included in Inventory Update transactions, ensuring accurate and complete inventory reporting. This issue has been resolved.
CMCP-41073 : Incomplete Mapping of Product Identifiers in PO Ack Messages	Web UI	In PO Ack messages, only the first entry in the "productCodesIdentifiers" array was mapped. This excluded additional identifiers like GTIN (Global Trade Item Number), NDC (National Drug Code), or IMN (Internal Material Number), leading to incomplete product data in the payload and inconsistencies with the ASN format. Mapping logic is updated to include all entries in the "productCodesIdentifiers" array. PO Ack messages now align with ASN format expectations and include GTIN, NDC, and IMN as required for accurate product identification. This issue has been resolved.

Known issues

Multienterprise Information Network Tower, solution version 16.0.0

There are no known issues in this release.

Tag end