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 19.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 2026.3.0 app release, which is available on Validation on 03 Sep 2026 and Production on 20 Sep 2026.

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

• Multienterprise Process Link, version 2026.3.0

  Solutions supported by this app version:

  • Multienterprise Information Network Tower, solution version 19.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

Revisions

Date	Revision	Description
20 Aug 2026	01	Initial version.
3 Sep 2026	02	The following updates have been made since the previous revision was distributed: The Production release date is updated from 04 Oct 2026 to 20 Sep 2026 in Release information section. The Expanded Logistics Orchestration Support for 4PL Operations feature is added. 16 issues are added to Resolved issues. 1 issue is added to Known issues.

API features

Multienterprise Process Link, version 2026.3.0

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

Send and Receive Customs Status Information in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Customs Status Information with their Partners via TraceLink in X12 format. Customs Status Information allows customs authorities to electronically communicate shipment status updates to authorized trading partners throughout the customs clearance process. Updates can include cargo release, cargo hold, and clearance progress. Authorized trading partners can include importers, exporters, customs brokers, customs agents, terminal operators, carriers, and service providers.

Exchanging Customs Status Information asynchronously via Multienterprise Process Link enables systems to automatically process and validate customs status updates, improving shipment visibility, reducing manual effort, accelerating customs clearance, and minimizing delays and processing errors.

Sending and receiving Customs Status Information asynchronously through Multienterprise Process Link enables companies and their Partners to:

• Search for, view, and troubleshoot Customs Status Information messages.

• Leverage a record of Customs Status Information details for business or compliance purposes.

• Retrieve the input, output, and canonical files for a specific Customs Status Information using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving Customs Status Information in this release:

• X12 (inbound and outbound):

  • B2B_EDI_X12_350_CustomsStatusInformation_IB_V1

  • B2B_EDI_X12_350_CustomsStatusInformation_OB_V1

Impact analysis

• Interface options:

  API

• Business segment impacts:
  • All business segments for both Owners and Partners

Send and Receive Customs Events Advisory Details in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Customs Events Advisory Details with their Partners via TraceLink in X12 format. Customs Events Advisory enables transportation organizations to electronically communicate significant cargo events to customs authorities and government agencies during international trade. Transportation organizations can include carriers, freight forwarders, and logistics providers. Cargo events can include arrivals, departures, transfers, in-bond movements, and other status updates.

Exchanging Customs Events Advisory Details messages asynchronously via Multienterprise Process Link enables consistent, accurate, and interoperable data exchange between transportation systems and customs authorities. This improves shipment visibility, supports customs compliance and regulatory reporting, reduces manual reporting efforts, and ensures timely communication of transportation events across trading partners.

Sending and Customs Events Advisory Details asynchronously through Multienterprise Process Link enables companies and their Partners to:

• Search for, view, and troubleshoot Customs Events Advisory Details messages.

• Access a record of the Customs Events Advisory Details message for business or compliance purposes.

• Retrieve the input, output, and canonical files for a specific Customs Events Advisory Details 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 Customs Events Advisory Details in this release:

• X12 (inbound and outbound):

  • B2B_EDI_X12_353_CustomsEventsAdvisoryDetails_IB_V1

  • B2B_EDI_X12_353_CustomsEventsAdvisoryDetails_OB_V1

Impact analysis

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

Send and Receive Motor Carrier Bills of Lading in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Motor Carrier Bills of Lading with their Partners via TraceLink in X12 format. Motor Carrier Bills of Lading enables shippers, brokers, and third-party logistics (3PL) providers to electronically communicate Bills of Lading information and transportation instructions to motor carriers before shipment pickup. Information can include shipment details, origin and destination information, freight descriptions, and special handling requirements.

Exchanging Motor Carrier Bills of Lading asynchronously via Multienterprise Process Link enables consistent and accurate communication while reducing manual paperwork and data entry errors. The transaction establishes the official record of the shipment, improves shipment accuracy, supports transportation and financial processes, enhances shipment visibility, and streamlines road freight operations.

Sending and receiving Motor Carrier Bills of Lading asynchronously through Multienterprise Process Link enables companies and their Partners to:

• Search for, view, and troubleshoot Motor Carrier Bills of Lading messages.

• Leverage a record of Motor Carrier Bills of Lading details for business or compliance purposes.

• Retrieve the input, output, and canonical files for a specific Motor Carrier Bills of Lading using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving Motor Carrier Bills of Lading in this release:

• X12 (inbound and outbound):

  • B2B_EDI_X12_211_MotorCarrierBillOfLading_IB_V1

  • B2B_EDI_X12_211_MotorCarrierBillOfLading_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.3.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.

Create New Discussion and Add Comment to Existing Discussion from Transaction View Page

For companies that own Multienterprise Process Link and their Partners, the All Discussions feature enables users to collaborate directly within subtype objects and their subtypes through integrated discussions, comments, and file attachments. Users can start discussions, add comments, and attach supporting documents, such as PDFs, images, and spreadsheets, directly from a subtype view, ensuring conversations and supporting evidence remain associated with the relevant object. By centralizing collaboration within MINT, this enhancement improves cross-company coordination, reduces reliance on external communication tools, and maintains an audit-ready history of discussions, comments, and attachments.

Feature highlights:

• Start discussions from a subtype view: Create a new discussion directly from any subtype view page.

• Add contextual comments: Keep updates, decisions, and collaboration associated with any subtype view page.

• Attach supporting files: Upload PDFs, images, spreadsheets, and other supporting documents to provide additional context and facilitate cross-company collaboration.

Impact analysis

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

Added Multi-Field Search Filter on all Transaction Search pages

Transaction Search pages now include a Multi-Field Search filter by default. The filter allows users to search multiple indexed text fields with a single keyword instead of selecting individual fields.

When a keyword is entered, MINT searches the indexed text fields for the corresponding business object and returns matching results from fields such as transaction identifiers, descriptions, statuses, partner names, and other indexed transaction data.

The Multi-Field Search filter is available by default in the Filter Panel on all Transaction Search pages and cannot be removed by page authors.

Key Benefits:

• Search transaction records across multiple fields with a single keyword.

• Find information without knowing which field contains the value.

• Provide a consistent search experience across Transaction Search pages.

• Ensure the search filter is always available in the Filter Panel.

Impact analysis

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

Transaction Failed in ERP Due to Data Mismatch or configuration issues

The Redeliver Failed Transaction capability allows authorized MINT Owner users to redeliver failed outbound B2B transactions. Users must be assigned the MINT – Super Admin role to use this capability. An outbound B2B transaction can fail because of an ERP data mismatch or configuration issue. After the issue is corrected, the user can redeliver the same transaction directly from MINT. The trading partner does not need to resend the transaction.

Key Points

• Redelivers the same failed outbound B2B transaction directly from MINT.

• Reduces dependency on trading partners to resend failed transactions.

• Shortens transaction recovery time and improves operational efficiency.

• Gives MINT Owners greater control over failed transaction processing.

• The Redeliver action is available from the following pages:

  • Business Transaction view page

  • Serialization Traceability view page

Impact analysis

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

Expanded Logistics Orchestration Support for 4PL Operations

Logistics Orchestration now supports Fourth-Party Logistics (4PL) operating models for Purchase Orders (PO) and Advance Shipment Notices (ASN) transactions. This enhancement enables 4PL providers to send operational and shipment information directly to their clients, providing centralized visibility across the shipment lifecycle.

Unlike the 3PL Commerce Orchestration model, where the client sends transaction and fulfillment information to the logistics provider for execution, the 4PL model supports the reverse flow. The logistics provider sends relevant PO and ASN information to the client, helping them monitor activities managed on their behalf across 3PLs, carriers, freight forwarders, warehouses, customs brokers, and other logistics partners.

Impact analysis

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

PickLists for MPL and Canonical Object Fields

MINT now provides standard PickLists for selected fields in Master Product List subtypes and Canonical Objects. These PickLists offer a consistent set of values for applicable fields, replacing manually defined values with standardized options. This enhancement improves data consistency, reduces the risk of manual entry errors, and supports more reliable processing and integrations across MINT.

Impact analysis

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

Standard Reports in Transportation Orchestration

In this release new Transportation orchestration base reports are now available. These reports provide a standardized starting point for monitoring transportation workflows and reviewing transaction activity.

Users can use the reports to gain greater visibility into transportation-related operational data. They can review relevant transaction details and analyze orchestration activity. Users can also filter, group, and select data based on their operational needs.

Impact analysis

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

Stabilization and usability enhancements

• MINT now provides more control and visibility for inbound shipment processing. Shipment events from Serialized Operations Manager and STE are processed only when enabled for a Process Network, which helps prevent unintended processing. Existing configured customers are migrated automatically to preserve their current workflows.
• MINT also sends automated notifications for shipment processing failures caused by B2B transformation errors or missing location identifiers for unlinked Partners. These notifications help administrators identify and troubleshoot shipment processing failures.

• This release includes the following user interface improvements:

  • The line item information reference transaction now displays the View Panel and shows the transaction type in the page header.

  • The Product Activity Search page now supports saving filters that include the productActivityPurposeCode field without errors.

  • The View Panel is now available for subline-item temperature and dangerous goods details in the Ocean Shipment Booking Request workflow.

  • The View Panel access button is restored on the Supplier_extManufacturingSentRemittanceAdvice page, enabling access to invoice and adjustment details.

  • The Price Authorization Acknowledgment customer and supplier views now correctly display the New button, restore the edit and currency panels, and support creating related reference transactions.

  • The View button is now available for nested line items in Third Party Logistics Sent Shipping Advice, providing access to detailed line item information.

  • Shipment Dimensions are now available in the Stop Point and Shipment Details sections of Motor Carrier Load Tenders, making shipment size information easier to review.

Impact analysis

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

Resolved issues

Multienterprise Process Link, version 2026.3.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- 38376: Inventory Balance Displayed Incorrect Reporting Location Values	API	In Logistics Orchestration, the Reporting Location attribute in the Inventory Balance transaction displayed transaction types, such as Purchase Order, Sales Order, and Invoice, instead of valid location types, such as GLN and Company ID. To fix this issue, the Inventory Balance subtype schema is updated to displays the correct location type values, such as GLN and Company ID, for the provider in the Logistics Orchestration UI. This issue has been resolved.
CMCP- 43026: Copy Into PO Ack Line Item Edits Not Retained	API	When creating a Purchase Order Acknowledgment (PO Ack) from a Purchase Order using Copy Into, line item edits such as quantity or delivery date changes were not retained after the PO Ack was completed. To fix the issue, the PO Ack maps are updated to retain line item edits ensure that the updated values are reflected in the MINT UI and the generated output file. This issue has been resolved.
CMCP- 43094: ASN Reports Failed to Load in OPUS Reports and Dashboards	API	OPUS Reports and Dashboards (ORD) reports for Advance Shipment Notice (ASN) transactions failed to load when some transactions did not contain all requested fields, preventing users from viewing the transaction data. To fix the issue, MINT updated the search handler logic to allow ORD reports for ASN transaction data to complete successfully even when some transactions do not contain all requested field values. This issue has been resolved.
CMCP- 43305: Supplier ASN Line Items Could Not Be Deleted	API	In MINT for Suppliers, added line items could not be removed from the Advance Shipment Notice (ASN) line item table when the transaction was opened for viewing or editing. To fix the issue, the line item table configuration is updated, and the Remove button now removes added line items as expected. This issue has been resolved.
CMCP- 43411: Empty Rows Displayed in Stop Point and Shipment Information Tables	API	In the Motor Carrier Load Tender transaction additional blank rows displayed in the Stop Point and Shipment Information table because required mapped attributes were not available in the MINT UI. To fix the issue, the rows are mapped correctly so that all required row details display as expected in the UI. This issue has been resolved.
CMCP- 43613: Inbound Receiving Advice Acceptance Transactions Fail During Processing	API	Inbound Receiving Advice Acceptance transactions containing invoice party reference identifiers remained in Processing and failed validation because the schema did not support those identifiers. To fix the issue, the schema is updated to support reference identifiers, allowing inbound Receiving Advice Acceptance transactions to pass validation and process successfully. This issue has been resolved.
CMCP- 43695: Line-Level Tax Information Not Mapped for Inbound Invoice	API	The Inbound X12 Invoice transactions did not support mapping for the line-level TXI segment. As a result, tax information provided at the invoice line level was not captured through the standard inbound invoice processing flow. To fix the issue, the transform is updated to map the line-level TXI segment, enabling the transactions to retain and process tax information for each line item. This issue has been resolved.
CMCP- 43752: Sender or Receiver IDs Intermittently Missing in the MINT UI	API	For some transaction workflows, sender or receiver IDs intermittently did not appear in the MINT UI due to a timeout while retrieving the associated network information. To fix the issue, MINT was updated to retry the request when a timeout occurs while retrieving network information. This helps ensure sender and receiver IDs are populated consistently in the MINT UI. This issue has been resolved.
CMCP- 43803: Incorrect IMN Codes Used in Sales Shipment Reports	API	In MINT sales shipment reporting, output files for serialized products handled by multiple Contract Manufacturing Organizations (CMOs) defaulted to an incorrect Internal Material Number (IMN), resulting in an IMN that did not match the applicable product and CMO combination. To fix the issue, the transformation logic is updated to select the correct IMN based on the relevant product and CMO context. This issue has been resolved.
CMCP- 43860: MINT Transactions Failed When Required Data Was Temporarily Unavailable	API	MINT transactions failed when NAA or master data services were intermittently unavailable during processing, preventing the required data from being retrieved during processing. To fix the issue, additional handling is added to reprocess and resume affected transactions directly from the MINT UI once NAA or the required master data becomes available, eliminating the need to resend the transaction. This issue has been resolved.
CMCP- 43884: Inventory Balance Reports Did Not Support Multi-Line Inventory Fields	API	The Inventory Balance schema did not include the fields and values required to support multi-line inventory reports, including lot approval, ownership, release, quarantine, and production material state details. To fix the issue, schema and related mappings are updated to support inventory reporting requirements. New attributes and values were added for lot approval status, lot ownership, lot release status, quarantine notes, quarantine reason codes, bulk material, and in-progress material states. Inventory Balance mappings across Commerce, External Manufacturing, and Logistics were also updated so multi-line inventory report data is processed and represented correctly. This issue has been resolved.
CMCP- 43908: Purchase Order Reports Missing Required Field Data	API	Purchase Order (PO) reporting did not include several required PO fields because the fields were not available in ORD. This limited the information available for reports and dashboard column mapping, including requested delivery and shipment dates, vendor details, vendor addresses, and product item descriptions. To fix the issue, ORD support for PO reporting was enhanced to make the required purchase order fields available. The missing fields are included in PO reports and reporting dashboard column mappings. This issue has been resolved.
CMCP- 43913: Purchase Order Values Were Not Supported for Mapping	API	Purchase Order transactions included charge, tax, summary, amount, and Unit of Measure (UOM) values that were not supported by the existing canonical value set. As a result, these values could not be mapped consistently during transaction processing, which could affect data accuracy, downstream reporting, or integration scenarios. To fix the issue, the canonical model is updated to include the required enumeration values, and the UOM mappings are expanded to support additional source Units of Measure during transaction processing. This issue has been resolved.
CMCP- 43953: Decimal Formatting Caused Transaction Transformation Failures	API	Some transaction transformations failed when decimal values were provided without a leading zero, such as .68. These values caused a number validation error during processing because the format was not recognized as a valid number. To fix the issue, transformation handling was updated to support decimal values that do not include a leading zero. These values are standardized during processing, allowing affected transactions to transform successfully. This issue has been resolved.
CMCP- 43955: Forecast Plan Missing Required Line-Item Fields	API	The Forecast Plan canonical did not support several required line-item fields for forecast data, including destination country, supply lead time, and month-wise quantity ranges. To fix the issue, the canonical is updated to support the required line-item mappings. Destination country can now be captured using ISO ship-to country codes, supply lead time can be captured in days, and month-wise quantity ranges can now be represented for forecast period quantities. This issue has been resolved.
CMCP- 44029: Party ID Values Missing from Copy Into Transactions	API	MINT mappings did not extract alternate location identifiers for ship-to location details. As a result, Purchase Order Acknowledgments, Advance Shipment Notices, and Invoices created using Copy Into could contain empty Party ID fields when the primary location identifier was unavailable. To fix the issue, mapping logic is updated to use the alternate location identifier when the primary location identifier is unavailable. Party ID values now populate correctly in the MINT UI and downstream output files generated through the Copy Into action. This issue has been resolved.

Known issues

Multienterprise Process Link, version 2026.3.0

The following known issues are included in this release and will be fixed in a future patch release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.

ID	Interface	Issue Description
TL-118696: Incorrect Copy Into configration for Logistics PO.	API	When using Copy Into from a Logistics Purchase Order (PO), the system incorrectly attempts to copy PO data into a Logistics Invoice sent by the logistics partner instead of a Commerce Invoice sent by the MAH to downstream partners. This results in an unsupported transaction creation path. To prevent this issue, the Invoice Copy Into button has been removed from the affected pages.

Tag end