What's new in the API and system
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 17.0.0 that provides the user interface for this app, see
Release information
This document describes the TraceLink capabilities included in the Multienterprise Process Link, version 2026.1.0 app release, which is available on Validation on 14 Mar 2026 and Production on 29 Mar 2026.
The following apps are impacted by this release and will be updated to the version listed:
- Multienterprise Process Link, version 2026.1.0
Solutions supported by this app version:
- Multienterprise Information Network Tower, solution version 17.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.
Revisions
| Date | Revision | Description |
|---|---|---|
| 19 Feb 2026 | 01 | Initial version. |
| 14 Mar 2026 | 02 | The following updates have been made since the previous revision was distributed:
|
Transaction canonical guidelines now available
Transaction canonical guidelines are now available that provides a standardized approach for mapping transaction-related business data into TraceLink’s canonical format to support consistent data exchange across systems. By aligning integrations with the TraceLink canonical model, customers and integration developers can ensure that transaction data is interpreted and exchanged consistently across connected systems. This standardization reduces ambiguity, improves interoperability, and simplifies the integration process. The guidelines also help accelerate on-boarding for new integrations and support scalable, maintainable data exchange across supply chain work flows.
For detailed information about the canonical structure and mapping guidelines, see Transaction canonical guidelines.
API features
Multienterprise Process Link, version 2026.1.0
The following new or updated API functionality is included in this release.
Send and Receive Application Advices in X12 Format
Companies that own or link to Multienterprise Process Link can exchange Application Advices with their Partners via TraceLink in X12 format. Application advices are bi-directional transactions that communicate the results of application-level business validations for previously received EDI transactions. They notify trading partners of errors, exceptions, or processing outcomes and may provide details on required corrections. A trading partner such as a manufacturer, wholesaler, distributor, or EDI solution provider sends an application advice if business rule validation identifies issues, after an EDI transaction passes syntax validation. Exchanging application advices asynchronously through Multienterprise Process Link enables structured, actionable feedback that helps trading partners quickly resolve business-level issues. This reduces delays, rejections, and manual investigation across integrated supply chain workflows, improving overall efficiency and data quality.
Sending and receiving application advices asynchronously through Multienterprise Process Link enables companies and their Partners to:
-
Search for, view, and troubleshoot Application Advice messages.
-
Leverage a record of Application Advice details for business or compliance purposes.
-
Retrieve the input, output, and canonical files for a specific Application Advice using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving application advices in this release:
- X12 (inbound and outbound):
- B2B_EDI_X12_824_ApplicationAdvice_IB_V1
- B2B_EDI_X12_824_ApplicationAdvice_OB_V1
Impact analysis
- Interface options:
API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Organizational Relationships in IDoc and X12 Formats
Companies that own or link to Multienterprise Process Link can exchange Organizational Relationships with their Partners via TraceLink in IDoc and X12 formats. Organizational Relationships is a master data transaction used to share structured information about hierarchies, relationships, and identifiers between trading partners. It allows the partner that owns or manages organizational data, such as a retailer, distributor, manufacturer, MAH, 3PL, or master data hub, to share that structure with partners who must align to it, including suppliers, CMOs, wholesalers, and distributors. The exchange is bi-directional, depending on which party owns the data and which needs to adopt it. Exchanging organizational relationship messages asynchronously via Multienterprise Process Link allows customers to standardize party, location, and relationship data once. This reduces errors and on-boarding time, aligns POs, ASNs, and invoices with fewer exceptions, and eliminates repetitive B2B data exchange.
Sending and receiving organizational relationships asynchronously through Multienterprise Process Link enables companies and their Partners to:
-
Search for, view, and troubleshoot organizational relationship messages.
-
Access a record of the organizational relationship message for business or compliance purposes.
-
Retrieve the input, output, and canonical files for a specific organizational relationship message using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving organizational relationships in this release:
- X12 (inbound):
B2B_EDI_X12_816_OrganizationalRelationships_IB_V1
B2B_EDI_X12_816_OrganizationalRelationship_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Shipments in IDoc and X12 Formats
Companies that own or link to Multienterprise Process Link can exchange Shipments with their Partners via TraceLink in IDoc and X12 formats. The Shipment exchange enables the transfer of shipment data between systems. Logistics Execution – Transportation (LE‑TRA) acts as the system of record and generates a shipment document when shipment data is created or updated. External systems, such as transportation management systems (TMS), carriers, 3PL providers, or other SAP instances receive the document and use the data for shipment planning, execution, visibility, and freight settlement. Exchanging shipment asynchronously via Multienterprise Process Link enables shipment-level communication across logistics networks, reducing complexity, improving visibility, and supporting efficient, automated transportation workflows. Previously, Partners relied on delivery‑level messages or manual handoffs to share the same shipment information.
Sending and receiving shipments asynchronously through Multienterprise Process Link enables companies and their Partners to:
-
Search for, view, and troubleshoot shipment messages.
-
Leverage a record of shipment details for business or compliance purposes.
-
Retrieve the input, output, and canonical files for a specific shipment using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving shipments in this release:
- IDoc (inbound):
- B2B_IDoc_SHPMNT04_Shipment_IB_V1
- X12 (outbound):
- B2B_X12_856_Shipment_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Text Messages in X12 Format
Companies that own or link to Multienterprise Process Link can exchange Text Messages with their Partners via TraceLink in X12 format. Text messages are bi-directional transactions that allow partners to share non-transactional, free-form messages that support business operations or clarify other EDI exchanges, such as operational notices (e.g., system outages, shipping delays, or product recalls), compliance or regulatory communications (e.g., DSCSA guidance), clarifications related to prior EDI messages, and general alerts or business updates delivered through EDI channels. It provides a standardized digital alternative to email, fax, or phone calls for messages that require interpretation or action by people. Exchanging text messages asynchronously via Multienterprise Process Link ensures critical updates, clarifications, and alerts are delivered quickly and consistently reducing delays, confusion, and manual follow‑up across trading partner relationships. Previously, Partners relied on email, phone calls, or other external tools to share the same information.
Sending and receiving text messages asynchronously through Multienterprise Process Link enables companies and their Partners to:
-
Search for, view, and troubleshoot text messages.
-
Access a record of the text messages for business or compliance purposes.
-
Retrieve the input, output, and canonical files for a specific text message using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving text messages in this release:
- X12 (inbound and outbound):
B2B_EDI_X12_864_TextMessage_IB_V1
B2B_EDI_X12_864_TextMessage_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners.
System features
Multienterprise Process Link, version 2026.1.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.
New Operational Dashboards in MINT
In this release, we introduced a comprehensive set of new dashboards in Multienterprise Information Network Tower to provide enhanced visibility across Procure-to-Pay (P2P), Order-to-Cash (O2C), manufacturing, inventory, and shipment. These dashboards deliver real-time operational insights, improve cross-functional transparency, and support faster decision-making. Together, these dashboards enhance operational transparency across supply chain and financial processes, enabling stakeholders to monitor performance, identify exceptions, and drive process optimization within MINT. 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 Warehouse Shipping Advice canonical model has been enhanced to improve how integrations represent shipment and charge details.
-
Added support for a distinct sold-to party at the shipment header and a structured header-level dates group for consistent key business dates.
-
Introduced an item-level order status code to align with X12 W12 requirements, including partial shipment scenarios.
-
Added a header-level action or status code to capture create, transfer, and other shipment actions.
-
Extended shipment charge options to include FOB Port of Call for more precise shipping term representation.
The Warehouse Stock Transfer Receipt Advice model has been enhanced to improve visibility into 3PL stock transfer events:.
-
Added warehouse entity information at the message root to clearly identify the warehouse responsible for the receipt for both sent and received 3PL advices.
-
Introduced a new Unloaded date type and Unloaded Date field to track when stock was physically unloaded.
-
Updated the canonical schema and subtype definitions to ensure consistent field availability across 3PL receipt flows.
Enhanced Ocean Shipment Status subtypes to support an expanded equipmentTypeISOCode list, preventing validation errors when processing container ISO codes.
Support for additional SAP inventory movement types, enabling more accurate tracking of inventory status changes and inventory differences across Inventory Update. subtype.
Enhanced Purchase Order canonical and subtypes (PO3) to support additional processing functions, credit and charge handling, quantity types, delivery zone and store details, and supplier-specific item details for richer order collaboration.
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 2026.1.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-41315: Double File Extensions in Transaction Input and Output Files | API |
All transaction types were producing input and output files with duplicate file extensions. This issue occurred even after the extension type is removed from the Integration Catalog, resulting in file names that contain repeated extensions across all supported formats. To fix this issue, the file naming configuration is updated to ensure that only a single file extension is appended during file generation. This issue has been resolved. |
| CMCP-41321: Missing Support for SAP Movement Types | API |
SAP movement types 341, 342, 711, and 712 were not supported in the inbound and outbound Inventory Update IDOC flow. These movement types were not included in the canonical schema, preventing proper mapping and processing within the existing integration framework. To fix this issue, support for SAP movement types 341, 342, 711, and 712 are added to the Inventory Update IDOC flow. The canonical data model, associated subtypes, and IDOC transformation logic is updated to ensure accurate mapping and processing for both inbound and outbound transactions. This issue has been resolved. |
| CMCP-41588: PO Failure Due to Missing Broker License Support | API |
Inbound X12 Purchase Orders were failing when the Bill-To Broker License (2969) was provided in the N1*BT segment (N103 = 36). The identifier was not supported in the existing mapping. To fix this issue, the inbound X12 PO map and canonical structures are updated to support mapping and processing of the Bill-To Broker License, enabling successful PO processing. This issue has been resolved. |
| CMCP-41646: View Details Panels Missing in Ocean Shipment Booking Request View Page | API |
After creating an Ocean Shipment Booking Request transaction, the view page did not display the "Item Details" and "Item Temperature and Dangerous Goods Details" panels. As a result, users could not review critical item information during transaction validation. This issue blocked shipment review and validation, reduced visibility, and potentially delayed processing. To fix this issue, the missing details panels is added to the Ocean Shipment Booking Request view page. Validated the update through end-to-end testing to ensure item information displays correctly. This issue has been resolved. |
| CMCP-41647: Ocean Shipment Booking Request Failure Due to Missing Unit of Measure field | API |
Ocean Shipment Booking Request transactions sent through the MINT UI failed during outbound processing because the "Unit of Measure" field was not available in the "Item Temperature and Dangerous Goods Details" panel, preventing users from completing bookings for temperature-sensitive or hazardous items and disrupting shipment processing. To fix this issue, the "Unit of Measure" field is added to the "Item Temperature and Dangerous Goods Details" panel to support successful outbound processing of Ocean Shipment Booking Requests. This issue has been resolved. |
| CMCP-41667: Inconsistent Equipment Codes in Shipment Status | API |
Inconsistent handling of equipment codes and transaction identifiers in Ocean shipment status messages caused data population discrepancies and processing challenges. As a result, shipment status information displayed inconsistently, affecting data accuracy and downstream processing. To fix the issue, a standardized ISO equipment code picklist is implemented and the mapping logic is enhanced to support non-unique equipment codes using a non-validated RFT text attribute and deployed the necessary updates to ensure consistent and accurate data population. This issue has been resolved. |
| CMCP-41932: Incorrect Last Modified Value Displayed on Shipping Instructions Search Pages | API |
The "Last Modified" attribute on all four Shipping Instructions transaction search pages displayed the user who last updated the record instead of the actual time stamp. This issue was caused by incorrect attribute mapping, where "Last Updated by User" was used instead of "Last Updated Date" Time. As a result, users could not view the accurate date and time of the last modification, reducing visibility into record updates. To fix the issue, the attribute mapping is corrected across all four search pages to display the "Last Updated Date Time", ensuring accurate modification details in the UI. This issue has been resolved. |
| CMCP-41949: Missing Data Visibility and Incorrect Field Mappings for Invoice IDoc Fields | API |
Some critical Invoice IDoc fields did not display correctly in the UI due to mapping gaps and incorrect field mappings. As a result, users could not view complete invoice information, impacting data accuracy and visibility. To address the issue, the mapping logic is updated and enhanced the related subtypes to resolve field gaps. Implemented custom mapping to support concatenation of shipping remarks, ensuring all finalized attributes display correctly in the UI. This issue has been resolved. |
| CMCP-42022:Line Item Validation Issue Impacting Transaction Accuracy | API |
The value "US_NDC" was not supported as a valid option for the "productCodeType" attribute in the subtype. In addition, decimal values entered in the "creditDebitAmount" attribute could not be saved. As a result, users were unable to select "US_NDC" for line items or save decimal "credit/debit" amounts, affecting transaction accuracy and processing. To fix this issue, "productCodeType" is updated to support "US_NDC" as a valid Line Item picklist value and enhanced "ext_TRACELINK_creditDebitAmount" to allow decimal values up to four places, ensuring accurate data entry and processing. This issue has been resolved. |
| TL-98028: Outbound Transaction Failure Due to Missing Unit of Measure Attribute | API |
Ocean Shipment Booking Confirmation transactions sent through the MINT UI failed during outbound processing because the "Unit of Measure" attribute was missing from the "Item Temperature & Goods Details" panel. As a result, transactions failed during outbound processing with a validation error. Users were unable to successfully complete outbound transactions, affecting shipment processing. To fix this issue, the "Unit of Measure" attribute is added to the relevant panels and the view screen table to ensure successful validation and outbound processing. This issue has been resolved. |
Known issues
Multienterprise Process Link, version 2026.1.0
| ID | Interface | Issue Description |
|---|---|---|
| TL-99069: Incorrect Results When Using Filter Rows and Limit Rows Together | API |
Reports that use Filter Rows and Limit Rows together may return incorrect results. When both features are applied, Limit Rows is evaluated against the original data set rather than the filtered result set. As a result, reports may display fewer rows than expected or no rows at all, leading to empty or incomplete report output. Workaround:
|
Tag end
