What's new in the APIs

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

To learn more about what's new in the Multienterprise Information Network Tower, solution version 16.0.0 that provides the user interface for this app, see What's new in the user interface.

Release information

This document describes the TraceLink capabilities included in the Multienterprise Process Link, version 2025.4.0 app release, which is available on Validation on 11 Dec 2025 and Production on 03 Jan 2026.

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

Multienterprise Process Link, version 2025.4.0
Solutions supported by this app version:
- Multienterprise Information Network Tower, solution version 16.0.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

This Help Center is subject to change based on the successful deployment of the release. In the event of changes, the Help Center will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.

Patch releases

The following patch is released for this version:

Multienterprise Process Link, version 2025.4.0M1 is available on Validation on 16 Dec 2025 and Production on 03 Jan 2026.

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: 9 issues are added to Resolved issues. 0 issues are added to Known issues.
16 Dec 2025	03	The following updates have been made since the previous revision was distributed: Issue information for the Multienterprise Process Link, version 2025.4.0M1 patch is added: 1 issue is added to Resolved issues. 0 issues are added to Known issues.

API features

Multienterprise Process Link, version 2025.4.0M1

There is no new or updated API functionality included in this release.

Multienterprise Process Link, version 2025.4.0

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

Send and Receive Handling Movement Instructions in EDIFACT Format

Companies that own or link to Multienterprise Process Link can exchange Handling Movement Instructions with their Partners via TraceLink in EDIFACT format. Handling Movement Instructions allow manufacturers, brand owners, and logistics providers to send standardized instructions such as transferring, blocking, releasing, or scrapping inventory with warehouses, distribution centers, or third-party logistics providers (3PLs). Exchanging handling movement instructions asynchronously via Multienterprise Process Link reduces manual processing, ensures consistent execution, and supports compliance with internal quality policies and external regulations.

Sending and receiving handling movement instructions asynchronously through Multienterprise Process Link enables companies and their Partners to:

Search for, view, and troubleshoot Handling Movement Instruction messages.
Leverage a record of Handling Movement Instruction details for business or compliance purposes.
Retrieve the input, output, and canonical files for a specific Handling Movement Instruction using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving handling movement instructions in this release:

EDIFACT (inbound and outbound):
- B2B_EDI_EDIFACT_HANMOV_HandlingMovementInstruction_IB_V1
- B2B_EDI_EDIFACT_HANMOV_HandlingMovementInstruction_OB_V1

Impact analysis

Interface options:
Business segment impacts:
- All business segments for both Owners and Partners

Send and Receive Ocean Shipment Booking Requests in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Ocean Shipment Booking Requests with their Partners via TraceLink in X12 format. 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. Exchanging ocean shipment booking requests asynchronously via Multienterprise Process Link enables faster coordination, better planning, and improved reliability across global shipping and intermodal logistics networks.

Sending and receiving ocean shipment booking requests asynchronously through Multienterprise Process Link enables companies and their Partners to

Search for, view, and troubleshoot ocean shipment booking request messages.
Leverage a record of ocean shipment booking request details for business or compliance purposes.
Retrieve the input, output, and canonical files for a specific shipment booking request using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving ocean shipment booking requests in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_300_OceanShipmentBookingRequest_IB_V1
- B2B_EDI_X12_300_OceanShipmentBookingRequest_OB_V1

Impact analysis

Interface options:
- API
Business segment impacts:
- All business segments for both Owners and Partners

Send and Receive Ocean Shipment Booking Confirmations in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Ocean Shipment Booking Confirmations with their Partners via TraceLink in X12 format. 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. Exchanging ocean shipment booking confirmations asynchronously via Multienterprise Process Link ensures accurate communication, operational readiness, and supply chain reliability by giving all stakeholders a shared, confirmed view of the booking details before any goods are moved.

Sending and receiving ocean shipment booking confirmations asynchronously through Multienterprise Process Link enables companies and their Partners to:

Search for, view, and troubleshoot shipping instruction messages.
Access a record of the shipping instruction for business or compliance purposes.
Retrieve the input, output, and canonical files for a specific shipment booking confirmation using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving ocean shipment booking confirmations in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_301_OceanShipmentBookingConfirmation_IB_V1
- B2B_EDI_X12_301_OceanShipmentBookingConfirmation_OB_V1

Impact analysis

Interface options:
- API
Business segment impacts:
- All business segments for both Owners and Partners

Send and Receive Shipping Instructions in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Shipping Instructions with their Partners via TraceLink in X12 format. 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. Exchanging shipping instructions asynchronously via Multienterprise Process Link enable accurate, timely, and consistent communication, ensuring that every shipment is executed correctly, on time, and according to plan.

Sending and Receiving shipping instructions asynchronously through Multienterprise Process Link enables companies and their Partners to:

Search for, view, and troubleshoot shipping instruction messages.
Access a record of the shipping instruction for business or compliance purposes.
Retrieve the input, output, and canonical files for a specific shipping instruction using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving ocean shipment booking confirmations in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_304_ShippingInstruction_IB_V1
- B2B_EDI_X12_304_ShippingInstruction_OB_V1

Impact analysis

Interface options:
- API
Business segment impacts:
- All business segments for both Owners and Partners

System features

Multienterprise Process Link, version 2025.4.0M1

There is no new or updated system functionality included in this release.

Multienterprise Process Link, version 2025.4.0

The following new or updated system functionality is included in this release.These features are changes to the app to support another feature and do not have any impacts on their own.

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

This release introduces Multienterprise Information Network Tower 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 aligns with business goals enables faster, data-driven decisions. This enhancement supports both current and future transactions, giving each orchestration baseline 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

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

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 Process Link, version 2025.4.0M1

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

ID	Interface	Issue Description
CMCP-41171: Class Loading Failure in B2B Maps Causes Transaction Errors	API	Several B2B maps failed with a "java.lang.ClassNotFoundException" due to incorrect class name formatting. The issue occurred because the class names included the .jar file extension, which caused Java to misinterpret the class path. As a result, the following maps failed at runtime: Pre-Release Transform Names: B2B_EDI_X12_852_ProductActivity_OB_V3 B2B_EDI_X12_867_ProductTransferResaleReport_OB_V2 B2B_TL_XML_AdvanceShipNotice_IB_V2 B2B_IDoc_SHPORD_DELVRY03_ShipOrder_IB_V3 B2B_IDoc_INVRPT_INVRPT01_InventoryBalance_IB_V3 B2B_EDI_X12_852_ProductActivity_IB_V4 B2B_EDI_X12_844_ProductTransferAccountAdjustmentRequest_OB_V2 MPC_STE_EPCIS_Extensions_SerializedShipmentNotice_1_2_IB_V2 B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_OB_V6 B2B_IDoc_SHPCON_DELVRY07_ShipAdvice_IB_V3 MPC_STE_EPCIS_SerializedShipmentNotice_1_2_IB_V7 B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_OB_V3 MPC_STE_EPCIS_SerializedShipmentNotice_1_2_OB_V8 To fix this issue the ".jar" extension is removed from class names and the "MIMEType" configurations are corrected to restore proper class loading and ensure consistent transaction processing. This issue has been resolved.

Interface

Issue Description

CMCP-41171: Class Loading Failure in B2B Maps Causes Transaction Errors

API

Several B2B maps failed with a "java.lang.ClassNotFoundException" due to incorrect class name formatting. The issue occurred because the class names included the .jar file extension, which caused Java to misinterpret the class path. As a result, the following maps failed at runtime:

Pre-Release Transform Names:

B2B_EDI_X12_852_ProductActivity_OB_V3
B2B_EDI_X12_867_ProductTransferResaleReport_OB_V2
B2B_TL_XML_AdvanceShipNotice_IB_V2
B2B_IDoc_SHPORD_DELVRY03_ShipOrder_IB_V3
B2B_IDoc_INVRPT_INVRPT01_InventoryBalance_IB_V3
B2B_EDI_X12_852_ProductActivity_IB_V4
B2B_EDI_X12_844_ProductTransferAccountAdjustmentRequest_OB_V2
MPC_STE_EPCIS_Extensions_SerializedShipmentNotice_1_2_IB_V2
B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_OB_V6
B2B_IDoc_SHPCON_DELVRY07_ShipAdvice_IB_V3
MPC_STE_EPCIS_SerializedShipmentNotice_1_2_IB_V7
B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_OB_V3
MPC_STE_EPCIS_SerializedShipmentNotice_1_2_OB_V8

To fix this issue the ".jar" extension is removed from class names and the "MIMEType" configurations are corrected to restore proper class loading and ensure consistent transaction processing.

This issue has been resolved.

Multienterprise Process Link, version 2025.4.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-39423: Missing Line‑Level Fields in WSO Canonical Schema	API	The Warehouse Shipping Order (WSO) canonical schema was missing several important line‑level fields required for complete and accurate transaction data representation. Missing fields included stockStatusCode, consignmentIdentifier, isCaptureSerialNumbers, isBonded, isTaxed, VATCode, VATRate, lineType, and warehouseIdentifier. The absence of these attributes could result in incomplete data capture and inconsistencies during warehouse shipping order processing. The WSO canonical schema is enhanced to include all previously missing line‑level fields, ensuring data completeness and schema alignment across related processes. This issue has been resolved.
CMCP-39877: Missing ITD01 and ITD02 Fields in Invoice Submissions	API	An issue was identified during the submission of an invoice via the user interface to the partner. While the transaction was successful in the MINT UI, it ultimately failed because the ITD01 and ITD02 fields were not populated. According to the mapping specifications, these fields should be derived from the termsOfPaymentTypeCode and termsOfPaymentDateBasis, but they were absent in the Subtype UI. The ITD01 and ITD02 fields are integrated into the Subtype UI, ensuring they are populated correctly during invoice submissions. This issue has been resolved.
CMCP-40080: Missing Fields in WSO Outbound Canonical	API	The outbound canonical message for WSO was missing expected fields, including the "mpcadditionalAddressinformation" field. This omission resulted in incomplete address data being transmitted, potentially causing downstream integration or processing issues. The mapping logic in WSO is updated to include the expected fields in the outbound canonical. This ensures that the "mpcadditionalAddressinformation" field is now correctly populated, improving data accuracy and compliance with the required specifications for outbound transactions. This issue has been resolved.
CMCP-40619: Validation Failure in MINT SFTP Flow Due to Missing Identifier Fields	API	In the MINT SFTP integration flow, transactions were not being stored when either the "fileSenderNumber" or "fileReceiverNumber" fields were missing. This behavior was caused by validation failures in two base object fields "senderIdentifierType" and "receiverIdentifierType". These fields were configured as picklists, and when no value was provided, the system rejected the transaction during processing. The issue is resolved by updating the configuration of "senderIdentifierType" and "receiverIdentifierType" from picklist fields to text fields. This issue has been resolved.
CMCP-40873: Workflow Enablement Issue on Historical Transactions	API	Users encountered an issue where workflows could not be enabled for older transactions. Although MINT supported backward compatibility for updating objects and the object updates were completing successfully, the associated workflow continued to reference outdated MINT handlers for the initial workflow transition step (from the previous release). As a result, the workflow failed to resume or progress as expected. Enhancements have been implemented in MINT to ensure that workflows referencing older transactions now correctly recognize and support legacy handlers. This issue has been resolved.
CMCP-41053: Missing Attributes in Critical Statuses of Order Status Report	API	The Order Status Report system was missing critical statuses, such as Packing Planned, Packing Process Initiated, Packing Process Complete, Transfer to Plant Warehouse, and Quality Approval Received,under the "orderStatusCode" attribute in "orderItemStatusReport". The schema is updated to include the missing enumerations to support more complete reporting. This issue has been resolved.
CMCP-41073 : Incomplete Mapping of Product Identifiers in PO Ack Messages	API	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.
TL-86472: Transaction Inconsistencies Caused by Duplicate Request Processing	API	Some MINT transactions entered an inconsistent state when the same request was processed twice (“Double Pump”). This caused the system to re‑execute a workflow step that had already completed, resulting in an incorrect transaction state displayed in the UI. The workflow handler is enhanced with an idempotency check to ensure that duplicate requests do not trigger the same workflow step more than once. This update prevents inconsistent transaction states and ensures stable, accurate workflow execution. This issue has been resolved.
TL-88034: Inability to Add Line Items in WSO Transactions	API	Users were unable to add line items to Warehouse Ship Order transactions in the Logistics Orchestration workflow. This issue blocked users from completing or submitting the transaction, impacting the orchestration of outbound shipments. The underlying validation mechanism is corrected to allow line items to be successfully added or modified within WSO transactions. Users can now add all required product lines without errors and complete the shipping workflow as expected. This issue has been resolved.

Known issues

Multienterprise Process Link, version 2025.4.0M1

There are no known issues in this release.

Multienterprise Process Link, version 2025.4.0

There are no known issues in this release.

Tag end