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 15.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.3.0 app release, which is available on Validation on 25 Sep 2025 and Production on 09 Oct 2025.

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

  • Multienterprise Process Link, version 2025.3.0

    Solutions supported by this app version:

    • Multienterprise Information Network Tower, solution version 15.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
04 Sep 2025 01 Initial version.
25 Sep 2025 02 The following updates have been made since the previous revision was distributed:

API features

Multienterprise Process Link, version 2025.3.0

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

Send and Receive Ocean Shipment Statuses in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Ocean Shipment Statuses with their Partners via TraceLink in X12 format. Ocean shipment statuses allow ocean carriers to share updates on the movement and handling of freight shipments. These messages can include details such as container loading and vessel departures, port arrivals and transshipment’s, customs clearance status, delay notifications with reasons, and confirmation of delivery or handoff at the final port. Exchanging ocean shipment statuses asynchronously via Multienterprise Process Link gives carriers, brokers, and logistics partners a real-time view of shipment progress, reducing manual follow-ups, improving coordination, protecting quality, and ensuring timely delivery.

Additionally, sending and receiving ocean shipment statuses asynchronously via Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot ocean shipment status messages; leverage a record of their ocean shipment status details for business or compliance purposes; and retrieve the input, output, and canonical files for a given ocean shipment status 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 statuses in this release:

  • X12 (inbound and outbound):

    • B2B_EDI_X12_315_OceanShipmentStatus_IB_V1

    • B2B_EDI_X12_315_OceanShipmentStatus_OB_V1

Impact analysis

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

Send and Receive Ocean Shipment Arrival Notices in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Ocean Shipment Arrival Notices with their Partners via TraceLink in X12 format. Ocean shipment arrival notices allow ocean carriers or freight forwarders to notify the consignee when an ocean freight shipment is nearing or has arrived at its destination port. Ocean shipment arrival notice provides all the key details needed to prepare for receipt, including arrival date and time,and any charges due upon arrival. Exchanging ocean shipment arrival notice asynchronously via Multienterprise Process Link helps prevent delays, enhance coordination, and safeguard product quality by giving all supply chain partners a consistent view of shipment status for seamless collaboration.

Additionally, sending and receiving ocean shipment arrival notices asynchronously via Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot ocean shipment arrival notice messages; leverage a record of their ocean shipment arrival notice details for business or compliance purposes; and retrieve the input, output, and canonical files for a given ocean shipment arrival notice 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 arrival notices in this release:

  • X12 (inbound and outbound):

    • B2B_EDI_X12_312_OceanShipmentArrivalNotice_IB_V1

    • B2B_EDI_X12_312_OceanShipmentArrivalNotice_OB_V1

Impact analysis

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

Send and Receive E222 Purchase Orders in X12 and Java Formats

Companies that own or link to Multienterprise Process Link can exchange E222 Purchase Orders with their Partners via TraceLink in X12 and Java formats. E222 Purchase Order allows distributors, or downstream partners to request goods, which the supplier or MAHs then uses to plan production or shipping activities. E222 Purchase Orders are a secure, DEA-compliant electronic order format that allows trading partners to exchange controlled substance orders while reducing paperwork and accelerating fulfillment. Each E222 includes encrypted and digitally signed order data to ensure integrity and traceability. Exchanging E222 purchase orders asynchronously via Multienterprise Process Link ensures authenticity and supports regulatory requirements for handling controlled substances.

Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot E222 purchase order messages; leverage a record of their E222 purchase orders for business or compliance purposes; and retrieve the input, output, and canonical files for a given E222 purchase order using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving E222 purchase orders in this release:

  • X12 (inbound):
    • B2B_EDI_X12_850_E222_PurchaseOrder_IB_V1
  • Java (inbound and outbound):
    • B2B_Java_E222_BinaryToBase64_IB_V1
    • B2B_Java_E222_Base64ToBinary_OB_V1

Impact analysis

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

Send and Receive CSOS Validated Purchase Orders in X12 Format

Companies that own or link to Multienterprise Process Link can exchange CSOS Validated Purchase Orders with their Partners via TraceLink in X12 format. Controlled Substance Ordering System (CSOS) validated purchase orders are generated by the seller after the DEA has successfully validated the order’s digital signature, confirming that it meets all regulatory requirements and can be legally fulfilled. Exchanging CSOS validated purchase orders asynchronously via Multienterprise Process Link safeguard the integrity of the controlled substance supply chain and helps prevent delays caused by incomplete or invalid documentation.

Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot CSOS validated purchase order messages; leverage a record of their CSOS validated purchase order for business or compliance purposes; and retrieve the input, output, and canonical files for a given CSOS validated purchase order using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving CSOS validated purchase orders in this release:

  • X12 (inbound and outbound):

    • B2B_EDI_X12_850_CSOS_ValidatedPurchaseOrder_IB_V1

    • B2B_EDI_X12_850_CSOS_ValidatedPurchaseOrder_OB_V1

Impact analysis

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

Send and Receive Inventory Update Requests in EDIFACT Format

Companies that own or link to Multienterprise Process Link can exchange Inventory Update Requests with their Partners via TraceLink in EDIFACT format. Inventory update requests allow MAHs, distributors, 3PLs, or pharmacy to request an update a partner or central system on current stock status. An inventory update request transaction instructs changes to the status, usability, or location of stock within the supply chain. Exchanging inventory update requests asynchronously via Multienterprise Process Link update dispositions, direct warehouse movements, and adjust handling instructions, supporting compliance, product quality, and supply continuity while keeping operations synchronized in real time.

Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot inventory update requests messages; leverage a record of their inventory update requests details for business or compliance purposes; and retrieve the input, output, and canonical files for a given inventory update requests using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.

The following new messages are available for sending or receiving inventory update requests in this release:

  • EDIFACT (inbound and outbound):

    • B2B_EDIFACT_INVRPT_InventoryUpdateRequest_IB_V1

    • B2B_EDIFACT_INVRPT_InventoryUpdateRequest_OB_V1

Impact analysis

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

Send and Receive Inventory Update Confirmation in EDIFACT Format

Companies that own or link to Multienterprise Process Link can exchange Inventory Update Confirmation with their Partners via TraceLink in EDIFACT format. Inventory update confirmations allow 3PLs to notify suppliers or inventory owners that requested changes to stock disposition or usability, as specified in the Inventory Update Request, have been completed. It serves as a formal acknowledgment that updates to stock status, usability, or location have been applied as instructed. Exchanging inventory update confirmations asynchronously via Multienterprise Process Link ensures all partners share the same real-time data, aligns reported stock with actual movements, reduces discrepancies, creates an auditable record for compliance, speeds up mismatch resolution, and eliminates manual reconciliation for faster decisions.

Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot inventory update confirmation messages; leverage a record of their inventory update confirmation for business or compliance purposes; and retrieve the input, output, and canonical files for a given inventory update 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 inventory update confirmations in this release:

  • EDIFACT (inbound and outbound):

    • B2B_EDIFACT_INVRPT_InventoryUpdateConfirmation_IB_V1

    • B2B_EDIFACT_INVRPT_InventoryUpdateConfirmation_OB_V1

Impact analysis

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

Send and Receive All Discussions

For companies that own Multienterprise Process Link and their partners, the All Discussions menu enhances collaboration by allowing users to add, view, and manage comments and file attachments directly within the Multienterprise Information Network Tower application. All Discussions facilitates Owner–Partner communication, streamlines review workflows, and supports faster, more organized transactions.

Key Highlights:

  • Add and Manage: Multiple comments and attachments may be added to a review to support internal collaboration and external feedback tracking. Comments may be marked as internal to restrict visibility to the Owner’s company only.
  • Character Limit: Comments support up to 5,000 characters. An alert displays if the character limit is exceeded.
  • File Uploads: One or more files may be uploaded via drag-and-drop or by selecting the browse link. Supported formats include: .doc, .txt, .csv, .jpeg, .png, .pdf. Unsupported formats include: .rar, .xml, .exe.
  • View and Edit: The most recent comments and attachments appear first. Entries can be edited by their users, with a full audit trail maintained for all actions.
  • Permissions: Internal comments are visible and manageable only by members of the owning company.

Impact analysis

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

Standard Reports in External Manufacturing, Logistics, Commerce, and Transportation Orchestration

Companies that own Multienterprise Information Network Tower and their Partners can use standard reporting across all External Manufacturing, Logistics, Commerce, and Transportation orchestrations. This enhancement supports both existing and future transactions, giving each orchestration baseline visibility and access to scalable, actionable analytics.

  • Multienterprise Information Network Tower users can only view reports of data within the MINT solution. By default, each solution is deployed with a predefined set of reports. If the company is licensed for MINT, users see these standard reports in the left-hand navigation menu of the MINT UI.

  • Companies licensed for both Multienterprise Information Network Tower and Opus Solution Environment (OSE) can give authorized OSE users the ability to customize reporting by adding or removing reports from the configuration. Users with the appropriate roles can view the reports linked to the MINT solution.

In this release, the external manufacturing, logistics, commerce, and transportation orchestrations include the following standard report types:

  • Base Reports - Reports per transaction - single object report.
  • Joint Reports - Combined reports across the orchestrations and within the orchestration- multiple object report.

Impact analysis

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

System features

Multienterprise Process Link, version 2025.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.

Stabilization and usability enhancements

In this release, certain maps now convert implied decimal values into explicit decimal format. Some attributes, such as quantities, prices, and weights, may be provided in an implied decimal format. In X12 messages, certain fields are defined as implied decimals, which means the user must send the value without the decimal point and rely on the field definition to determine its placement. For example, an amount of value 123.40 with two implied decimals must be sent as the value 12340. This enhancement ensures consistent handling of numerical attributes across transactions, improving accuracy in storage, display, and partner data exchange.

The following maps convert implied decimal values into explicit decimal format:

  • CSOS Validated Purchase Order

    • B2B_EDI_X12_850_CSOS_ValidatedPurchaseOrder_IB_V1

    • B2B_EDI_X12_850_CSOS_ValidatedPurchaseOrder_OB_V1

  • E222 Purchase Order

    • B2B_EDI_X12_850_E222_PurchaseOrder_IB_V1

    • B2B_Java_E222_BinaryToBase64_IB_V1

    • B2B_Java_E222_Base64ToBinary_OB_V1

  • Inventory Update Request

    • B2B_EDIFACT_INVRPT_InventoryUpdateRequest_IB_V1

    • B2B_EDIFACT_INVRPT_InventoryUpdateRequest_IB_V1

  • Inventory Update Confirmation

    • B2B_EDIFACT_INVRPT_InventoryUpdateConfirmation_IB_V1

    • B2B_EDIFACT_INVRPT_InventoryUpdateConfirmation_OB_V1

  • Ocean Shipment Arrival Notice

    • B2B_EDI_X12_312_OceanShipmentArrivalNotice_IB_V1

    • B2B_EDI_X12_312_OceanShipmentArrivalNotice_OB_V1

  • Ocean Shipment Status

    • B2B_EDI_X12_315_OceanShipmentStatus_IB_V1E222 Purchase Order

    • B2B_EDI_X12_315_OceanShipmentStatus_OB_V1

To support new requirements, previously released TraceLink transactions have been enhanced with additional attributes and enumeration values. The following transactions and their underlying user interface schemas have been updated:

  • Purchase Order

  • Purchase Order Acknowledgment

  • Forecast Plan and Response

  • Invoice

  • Advance Shipment Notice

  • Warehouse Stock Transfer Receipt Advice

  • Inventory Balance

  • Carrier Shipment Status

  • Order Status Report

  • Product Activity

  • Product Transfer Resale Report

The following master data identifiers are now available for Multienterprise Information Network Tower customers to enable transaction exchange:

  • TRANSACTION_PARTY_ID

  • SPLC

  • UCC_COMM_ID

  • TELEPHONE_NUMBER

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.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-39667: Forecast Plan UI Displays Line Item Error for IDoc Transactions API

The Forecast Plan UI displayed only one line item instead of five for transactions initiated from an IDoc file. This occurred due to incorrect mapping logic for line item details.The mapping now supports X12, IDoc, and EDIFACT formats, each with unique hierarchical structures. The Forecast Plan UI correctly displays all line items for IDoc-based transactions.

This issue has been resolved.
CMCP-39741: Missing TRANSFER Value in quantityType of Product Transfer Resale Report API

The "TRANSFER" value in the "quantityType" field of the Product Transfer Resale Report was not available for use, even though it existed in the schema preventing the users from selecting it in reports. The schema has been updated to make ‘TRANSFER’ available.

This issue has been resolved.
CMCP-39786: Outbound ASN Fails with Error When Submitted via User Interface API

ASN submissions failed in the UI for transactions with multiple line items due to an incorrect default quantity type. The default was set to "DELIVERED", which is incompatible with multi-line ASNs under X12 and EDIFACT standards. ASNs created using "Copy Into" retained the correct value, but new ASNs defaulted to "DELIVERED", causing transformation errors. The ASN UI now assigns a valid quantity type for multi-line ASNs to ensure compatibility with X12 and EDIFACT standards and prevent transformation errors.

This issue has been resolved.
CMCP-39834: Invoice Type Missing from Invoice Subtype Data API

Outbound invoices were missing the "Invoice Type" because the UI did not allow users to set this value. As a result, the required "BIG07" field was not populated in the EDI map, causing issues with invoice processing. The UI and mapping logic is updated to include the Invoice Type, enabling correct population of the BIG07 field in the EDI map. As part of this update, additional fields such as "Terms of Payment Type Code", "Terms of Payment Date Basis", "Due Date", "Invoice Payer Entity Information", and "Ship To Location Information" are also included to support downstream processing and ensure compliance.

This issue has been resolved.
CMCP-39884: 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-39945: Missing YNQ segment in ASN API

The ASN was missing the "YNQ" segment, preventing capture of key fields "questionCode", "responseCode", "dateType", "dateValue", "freeFormText" and limiting data exchange. The ASN schema is updated to include the "YNQ" segment with all required fields, enabling complete shipment information sharing.

This issue has been resolved.
CMCP-39950: Missing Consumption Data segment in ASN and Warehouse Stock Transfer Receipt Advice API

The ASN and Warehouse Stock Transfer Receipt Advice schemas contained duplicate type definitions, which limited support for component consumption details. A new "componentConsumption" group with required attributes is added, replacing duplicates to ensure consistent data handling without introducing breaking changes.

This issue has been resolved.
CMCP-39988: Missing In-Transit Status Codes in Order Status Report API

The Order Status Report schema was missing in-transit codes and tags needed to support ocean shipments, track freight hold and release, and distinguish customs release at origin and destination. Missing in-transit status codes and tags are added, along with custom mapping, to ensure complete and accurate tracking of shipment statuses.

This issue has been resolved.
CMCP-40011: VENDORPART Product Code not Supported in Invoice and ASN API

The Invoice and ASN canonicals did not support the "VENDORPART (VP)" product code, preventing transmission of product data that required it and limiting compatibility with trading partner requirements. Invoice and ASN transactions now support the "VENDORPART (VP)" product code, enabling accurate capture, transmission, and processing of VP-based product information.

This issue has been resolved.
CMCP-40037: Missing Enumerations for dateType and invoiceType in Invoice Schema API

The Invoice schema was missing the "DOCUMENTDUE" enumeration in "dateType" and "DEBITMEMO" in "invoiceType", limiting support for due dates and debit memos. The Invoice schema is updated to include the missing enumerations, ensuring full support for due dates and debit memos in outbound invoices.

This issue has been resolved.
CMCP-40093: Missing Identifier Values in b2bTransactionIdentifierType for Transactions API

The "b2bTransactionIdentifierType" attribute did not include the "REVISIONNUMBER" and "CLINICALTRIALPROTOCOLNUMBER" values, limiting identifier support in Purchase Order, Purchase Order Acknowledgment, ASN, and X12 214 Carrier Shipment Status transactions. The schema is updated to add these enumeration values, ensuring complete identifier support and improving accuracy in B2B integrations.

This issue has been resolved.
CMCP-40117: Missing Attributes and Enumeration Values in the PO system model API

The Purchase Order (PO) was missing attributes and enumeration values, limiting the ability to capture shipment details, order status updates, and related identifiers. The PO was updated with new attributes such as "SHIPMENT_CANCELLED_FLAG", "shipmentOrderStatusCode", "Last Changed Date", expanded enumeration values, updated "warehouseIdentifier" ensuring complete and accurate processing of PO data.

This issue has been resolved.
CMCP-40125: ASN Date Missing Across All Statuses API

The system was not capturing ASN date for the statuses Created, In Progress, Completed, and Cancelled, preventing users from accurately tracking ASN lifecycle events. The system now captures and displays ASN dates for all the statuses, providing complete visibility into ASN timelines and improving shipment tracking.

This issue has been resolved.
CMCP-40126: Missing Date Fields in Order Status Report API

The Order Status Report was missing date fields for specific statuses, unindexed attributes and outdated UI mappings further limited visibility and accurate processing of order status updates. The Order Status Report schema and subtypes were updated to meet the requirements. New date fields and indexes were added, and the UI was updated to display the additional data—ensuring complete visibility and accurate tracking of order status updates.

This issue has been resolved.
CMCP-40127: Missing Fields in Invoice Inbound Schema API

The invoice data model was missing a descriptive field for the "Sold to Customer" (Wholesaler) designation, relying instead on "isSoldToCustomer". It was also missing enumeration mappings for common credit sub-reasons such as "Bad Weather", "Expiry Date Too Short", and "Wrong Product Picked". The schema is updated to include a new canonical field for "Sold to Customer" (Wholesaler) and expands the "creditChargeSubType" enumeration to support required credit sub-reasons.

This issue has been resolved.
CMCP-40157: Missing Fields in Forecast Plan Schema API

Missing fields in the Forecast Plan schema caused incorrect mapping and processing of forecast data, resulting in missing key details such as designators, quantity types, and address information, and leading to incomplete downstream processing. The Forecast Plan schema is updated to include missing fields, ensuring accurate mapping of designators, quantity types, and address information.

This issue has been resolved.
CMCP-40193: ASN Date Missing in Subtype API

The system was not capturing ASN date for the statuses Created, In Progress, Completed, and Cancelled, preventing users from accurately tracking ASN lifecycle events. The system is updated to capture and display ASN dates for all four statuses, providing complete visibility into ASN timelines and improving shipment tracking.

This issue has been resolved.
CMCP-40225: Missing Fields in Warehouse Shipping Advice Schema API

The Warehouse Ship Advice schema was missing transport-related values specifically, "M" (Motor/Common Carrier) for W2701 and did not clearly separate "Routing Sequence Code" from the "Transportation Method impacting accurate transmission of shipping details. The schema is updated to improve transport-related data mapping by adding the missing "M" value for "W2701" and clearly separating "Routing Sequence Code" from "Transportation Method".

This issue has been resolved.
TL-68295:Serialization Traceability Exchange Handler Fails to Log Response Returned by B2B API

In Serialization Traceability Exchange flows, the decider handler did not log B2B responses correctly, resulting in false errors even when valid responses were returned. The handler logic is updated to correctly log B2B responses, preventing false errors when valid responses are returned.

This issue has been resolved.

Known issues

Multienterprise Process Link, version 2025.3.0

There are no known issues in this release.

Tag end