View search and download B2B messages

Owners and their Partners search for and view serialized messages such as Purchase Orders (POs) purchase order acknowledgments Advanced Ship Notices (ASNs) and Invoices that are exchanged with Partners asynchronously

Whats new in Multienterprise Process Link version 202540

To learn more about whats new in the Multienterprise Information Network Tower solution version 1600 that provides the user interface for this app see Release information This document describes the TraceLink capabilities included in the Multienterprise Process Link version 202540 app release which is available on Validation on 11 Dec 2025 and Production on 10 Jan 2026 The following apps are impacted by this release and will be updated to the version listed Multienterprise Process Link version 202540 Solutions supported by this app version Multienterprise Information Network Tower solution version 1600 The features below are in order of functional relevance (ie the typical order in which a user executes a function or task) These release notes are subject to change based on the deployment of the release In the event of changes the release notes and any related documentation 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 202542 is available on Validation on 22 Jan 2026 and Production on 05 Feb 2026 Multienterprise Process Link version 202541M1 is available on Validation and Production on 15 Jan 2026 Multienterprise Process Link version 202541 is available on Validation and Production on 12 Jan 2026 Multienterprise Process Link version 202540M2 is available on Validation and Production on 03 Jan 2026 Multienterprise Process Link version 202540M1 is available on Validation on 16 Dec 2025 and Production on 03 Jan 2026 These patches are cumulative and the most recent patch release includes functionality from all previous versions 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 distributed9 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 distributedIssue information for the Multienterprise Process Link version 202540M1 patch is added 1 issue is added to Resolved issues 0 issues are added to Known issues 03 Jan 2026 04 The following updates have been made since the previous revision was distributedIssue information for the Multienterprise Process Link version 202540M2 patch is added 1 issue is added to Resolved issues 0 issues are added to Known issues 10 Jan 2026 05 The following update have been made since the previous revision was distributed The Production release date is updated from 03 Jan 2026 to 10 Jan 2026 for Production Frankfurt in Release information section 12 Jan 2026 06 The following updates have been made since the previous revision was distributedIssue information for the Multienterprise Process Link version 202541 patch is added 1 issue is added to Resolved issues 0 issues are added to Known issues 15 Jan 2026 07 The following updates have been made since the previous revision was distributedIssue information for the Multienterprise Process Link version 202541M1 patch is added 10 issues are added to Resolved issues 0 issues are added to Known issues 22 Jan 2026 08 The following updates have been made since the previous revision was distributedIssue information for the Multienterprise Process Link version 202542 patch is added 11 issues are added to Resolved issues 0 issues are added to Known issues API features Multienterprise Process Link version 202542 There is no new or updated API functionality included in this release Multienterprise Process Link version 202541M1 There is no new or updated API functionality included in this release Multienterprise Process Link version 202541 There is no new or updated API functionality included in this release Multienterprise Process Link version 202540M2 There is no new or updated API functionality included in this release Multienterprise Process Link version 202540M1 There is no new or updated API functionality included in this release Multienterprise Process Link version 202540 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 thirdparty 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) B2BEDIEDIFACTHANMOVHandlingMovementInstructionIBV1 B2BEDIEDIFACTHANMOVHandlingMovementInstructionOBV1 Impact analysis Interface options API Business segment impactsAll 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) B2BEDIX12300OceanShipmentBookingRequestIBV1 B2BEDIX12300OceanShipmentBookingRequestOBV1 Impact analysis Interface options API Business segment impactsAll 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) B2BEDIX12301OceanShipmentBookingConfirmationIBV1 B2BEDIX12301OceanShipmentBookingConfirmationOBV1 Impact analysis Interface options API Business segment impactsAll 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 thirdparty 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) B2BEDIX12304ShippingInstructionIBV1 B2BEDIX12304ShippingInstructionOBV1 Impact analysis Interface options API Business segment impactsAll business segments for both Owners and Partners System features Multienterprise Process Link version 202542 There is no new or updated system functionality included in this release Multienterprise Process Link version 202541M1 There is no new or updated system functionality included in this release Multienterprise Process Link version 202541 There is no new or updated system functionality included in this release Multienterprise Process Link version 202540M2 There is no new or updated system functionality included in this release Multienterprise Process Link version 202540M1 There is no new or updated system functionality included in this release Multienterprise Process Link version 202540 The following new or updated system functionality is included in this releaseThese features are changes to the app to support another feature and do not have any impacts on their own Introduction of MINT Dashboards TraceLinks 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 realtime visibility into their company’s data based on the business objects (eg Purchase Orders) that are relevant to their companys 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 datadriven 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 optionsWeb UI Business segment impactsAll 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 optionsWeb UI Business segment impactsAll 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 endtoend 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 IoTrelated 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 fieldlevel adjustments to align each transaction type with integration standards and business requirements Data Quality and Structural Issues The gap analysis found missing mandatory fields (eg 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 solutions stability and its ability to communicate with other TraceLink apps and solutions Impact analysis Interface optionsWeb UI Business segment impactsAll business segments for both Owners and Partners Resolved issues Multienterprise Process Link version 202542 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 CMCP40680 Inventory Balance Canonical Did Not Support HANMOV Inventory Movements API The Inventory Balance and Inventory Report canonical schema did not represent handling movement instructions received through EANCOM INVRPT messages As a result inventory movements statuses references quarantine information and partner or location context required for handling movement instruction scenarios were not accurately mapped or processed The schema now supports handling movement instructions from EANCOM INVRPT messages including inventory statuses partner and location details references and movement context to enable accurate processing and complete inventory reporting This issue has been resolved CMCP41264 Missing SAP Customer Material Number in ASN Outbound Mapping API The ASN outbound canonical mapping did not include the SAP customer material number from all relevant IDoc segments As a result outbound ASNs contain incomplete customer material information affecting customerspecific material identification and reconciliation The ASN outbound canonical mapping now includes applicable IDoc segments ensuring complete and consistent customer material information in outbound ASNs This issue has been resolved CMCP41360 Incomplete Support for Reject Reason and Purchaser Address Data in Product Transfer Account Adjustment X12 API Inbound Product Transfer Account Adjustment data contained reject reason codes and purchaser address information that were not supported by the canonical model preventing the standard Product Transfer Account Adjustment X12 transform from fully representing this data for downstream partners This fix ensures complete data exchange for Product Transfer Account Adjustments by updating the canonical and transform schemas improving accuracy compliance and partner interoperability This issue has been resolved CMCP41361 Limited Support for Purchase Order Tolerances and Component Details API The purchase order canonical model did not represent quantity and price tolerances provided at different life cycle stages such as Order Confirmation and Advance Ship Notice (ASN) In addition the model lacked sufficient fields to capture multiple component details for finished goods purchase orders with subcontracting or consumption components These limitations resulted in limited tolerance and component data for downstream integrations The schema now supports multiple tolerance rules and expanded componentlevel details while maintaining backward compatibility enabling accurate representation of quantity and price tolerances across lifecycle stages and complete transmission of component data in canonicalbased integrations This issue has been resolved CMCP41527 Missing Enumeration Support in PO Acknowledgment Canonical Schema API The PO Acknowledgment canonical schema did not support the "DE" (Deal) unit of measure or the "UNUPC" product code type for caselevel UPCs which prevented Purchase Order Acknowledgments using these standard values from being fully represented or exchanged with partners The schema now supports "DE" (Deal) and "UNUPC" enabling accurate representation of dealbased quantities and caselevel UPC product codes in standard PO Acknowledgment integrations This issue has been resolved CMCP41528 Incomplete Partner and Credit/Charge Support in Credit/Debit Adjustments API The Credit Debit Adjustment canonical schema did not support "Billto" and "Shipto" partner information or several standard credit and charge types used in X12 transactions In addition handling code mappings were incomplete for certain X12 formats These gaps limited accurate representation of partner details and financial adjustments for downstream integrations The schema now supports "Billto" and "Shipto" partner details expand credit and charge type coverage and complete handling code mappings for X12 transactions enabling accurate standardscompliant exchange of Credit Debit Adjustment data across partners This issue has been resolved CMCP41529 Missing Seller Invoice and Customer Reference Support in Payment/Remittance Advice API The Payment and Remittance Advice canonical schema did not support references to seller invoices or customerspecific identifiers As a result payment and remittance messages could not fully represent standard reference information required by downstream partners The schema now supports seller invoice and customer reference identifiers enabling complete standardsaligned payment and remittance messaging to improve reconciliation and partner interoperability This issue has been resolved CMCP41536 Carrier Shipment Status Messages Failed Due to Unsupported Shipped Date Type API Carrier Shipment Status messages sent was stuck in a "Processed" state with an error and no visible message in the UI These failures prevented transaction IDs from being generated and blocked downstream processing The data model now supports the Shipped date type resolving validation errors enabling successful transaction processing and ensuring transaction IDs are populated as expected This issue has been resolved CMCP41541 Missing LineLevel Data Support in Warehouse Shipping Orders API The Warehouse Shipping Order (WSO) canonical schema did not support required linelevel fields needed to represent stock status tax details and warehouse information As a result WSO mappings could not fully support downstream warehouse integrations The schema to include required linelevel attributes for stock status consignment serial capture tax and VAT line type and warehouse ID enabling complete and accurate WSO mappings for warehouse Partners This issue has been resolved CMCP41563 Limited Purchase Order Enumeration Support in Canonical Schema API The Purchase Order canonical schema did not support required identifier date partner entity and pricing values These gaps limited the ability to accurately represent certain Purchase Order scenarios in downstream integrations The schema now supports additional transaction IDs delivery date types partner entities and pricing classifications enhancing data completeness and ensuring consistent Purchase Order processing across integrations This issue has been resolved CMCP41574 Incomplete Invoice Canonical Support for Item Payment and Tax Details API The Invoice canonical schema did not support itemlevel attributes payment term options product code classifications and credit charge and tax types required to align with Purchase Order data These gaps limited accurate invoice representation and downstream integration processing The schema now supports extended item details payment terms and broader credit charge and tax classifications improving alignment with Purchase Order requirements and ensuring more consistent invoice data across integrations This issue has been resolved Multienterprise Process Link version 202541M1 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 CMCP38624 Inbound Purchase Order IDoc Mapping Gaps API The inbound IDoc transform for Purchase Orders did not map key data elements eg the VAT registration number plant identifier and batch number This limitation resulted in incomplete Purchase Order data potential compliance risks (eg missing VAT information) and increased manual effort to correct downstream records The transform is updated to map the VAT registration number plant identifier and batch number This fix ensures complete data capture improves downstream data accuracy and reduces the need for manual reconciliation PreRelease Transform Name B2BIDocORDERS05PurchaseOrderIBV7 This issue has been resolved CMCP40656 EDIFACT PO Acknowledgment Mapping and Validation Issues API The EDIFACT Purchase Order Acknowledgment inbound and outbound transforms applied outdated validations and incomplete mappings These limitations caused processing errors and inconsistent handling of contact details payment terms scheduling data and date values preventing alignment with updated specifications The transforms are updated to remove obsolete validations and align mappings with current standards This fix improves support for contact and payment details scheduled quantities and dates and canonical date types ensuring more reliable and standardscompliant processing PreRelease Transform Name B2BIDocORDERS05PurchaseOrderAcknowledgmentIBV5 B2BEDIEDIFACTORDRSPPurchaseOrderAcknowledgmentOBV4 This issue has been resolved CMCP40750 ASN Identifier Duplication Across Packaging Levels API Inbound ASNs failed when the same identifier was used at both the pallet and packaging levels "MAN*GM" segments must be unique at each hierarchy level and duplicate "SSCC" identifiers caused processing errors The mapping is updated to correctly evaluate "MAN*GM" segments at the packaging level before processing other MAN segments This fix enforces identifier uniqueness across hierarchy levels and prevents ASN processing errors PreRelease Transform Name B2BEDIX12856AdvanceShipNoticeIBV7 This issue has been resolved CMCP40798 Missing Inventory Status Code Support in Inventory Update IDocs API The Inbound and Outbound Inventory Update IDoc transforms did not support inventory status codes 331 332 503 and 504 As a result Inventory Update messages using these codes failed or processed incorrectly The transform is updated to support inventory status codes ensuring accurate and consistent inventory processing PreRelease Transform Name B2BIDocMBGMCRMBGMCR03InventoryUpdateIBV3 B2BIDocMBGMCRMBGMCR03InventoryUpdateOBV4 This issue has been resolved CMCP40878 Incorrect Line Item Reference Mapping for ASN Purchase Orders API For ASNs associated with Purchase Orders the inbound XML transform mapped line item references incorrectly This caused ASN line items to reference incorrect or missing Purchase Order line numbers leading to downstream processing issues The transform is updated to correctly map Purchase Order line item numbers when the reference type is Purchase Order This fix ensures accurate line item alignment between ASNs and Purchase Orders PreRelease Transform Name B2BTLXMLAdvanceShipNoticeIBV3 This issue has been resolved CMCP40907 Outbound Transaction Failure for Distributor Invoice Identifier API Outbound product transfer resale report transactions failed when the "b2bTransactionIdentifierType" field contained the value "DISTRIBUTORINVOICE" This value was not supported preventing successful outbound processing The transaction is updated to has been done to support the "DISTRIBUTORINVOICE" value This fix allows outbound transactions using this identifier type to process successfully PreRelease Transform Name B2BEDIX12867ProductTransferResaleReportOBV3 This issue has been resolved CMCP41031 Missing Component Information in EDIFACT Purchase Order Outbound Messages API The EDIFACT outbound transform for Purchase Orders did not include component product information As a result component identifiers quantities and lot details were not transmitted in outbound Purchase Order messages The transform is updated to map component product details including product codes consumed quantities with units of measure and lot numbers This fix ensures complete and standardsaligned transmission of component information PreRelease Transform Name B2BEDIEDIFACTORDERSPurchaseOrderOBV7 This issue has been resolved CMCP41126 Inventory Report Transform Limitations for Quantity Types and Effective Dates API The inbound Inventory Report transform did not support several inventory quantity type codes which could result in incomplete inventory reporting In addition the outbound Inventory Report transform incorrectly failed when an "EFFECTIVE" date was not provided even though this date is optional The transform now supports additional inventory quantity type codes ensuring accurate inventory status reporting The outbound Inventory Report transform is also updated to allow processing when an "EFFECTIVE" date is not present preventing unnecessary errors PreRelease Transform Name B2BIDocINVRPTINVRPT01InventoryBalanceIBV4 B2BIDocINVRPTINVRPT01InventoryBalanceOBV3 This issue has been resolved CMCP41193 Order Reference Handling Did Not Align with SAP Requirements API The transform enforced restricted values and relied on the "ORDERNUMBER" field which did not align with SAP requirements This mismatch caused order references to be processed incorrectly in outbound transactions The transform is updated to remove the restricted values check and use the "PURCHASEORDER" field as the order reference This fix aligns processing with SAP requirements and ensures correct order identification PreRelease Transform Name B2BIDocORDERS05PurchaseOrderOBV9 This issue has been resolved CMCP41449 Incorrect Unit of Measure Mapping for PK API The system mapped the unit of measure "PK" incorrectly as "PKPH" in canonical data This resulted in inaccurate unit of measure values in downstream processing The unit of measure mapping is corrected to map "PK" to "PK" in the canonical format This fix ensures accurate and consistent unit of measure values PreRelease Transform Name B2BIDocINVRPTINVRPT01InventoryBalanceIBV4 This issue has been resolved Multienterprise Process Link version 202541 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 CMCP41181 Unintended Duplicate Orders and Acknowledgments from a Single Purchase Order API In some instances a single purchase order triggers duplicate sales orders and acknowledgments during retries or errors increasing the risk of duplicate shipments and inaccurate financial reporting This behavior affects purchase order processing sales order generation financial reconciliation and shipment accuracy MINT reprocesses the same transaction during retries or internal errors causing downstream systems to handle the same purchase order multiple times The issue is fixed to process each transaction only once from initiation to completion This fix prevents duplicate transactions caused by retries network issues or other errors and ensures consistent results even when the same request is submitted multiple times This issue has been resolved Multienterprise Process Link version 202540M2 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 TL93169 Enhanced Delivery Transparency in Info Exchange API In some instances files sent through Info Exchange to major trading partners were marked as "Delivered" within the system However recipients either did not receive or could not locate the files This discrepancy between the system status and recipient acknowledgment impacted sender scorecards due to the absence of verifiable delivery evidence Info Exchange has been enhanced to provide greater delivery transparency through the inclusion of Message Disposition Notification (MDN) details Users can now view additional delivery information including the specific recipient connection used and the exact delivery timestamp These enhancements provide clear auditable evidence that files were successfully transmitted helping customers validate delivery with trading partners reduce delivery disputes and protect sender scorecards Delivery confirmation has been improved for the following X12 and EDIFACT transaction types X12850 Purchase Order Purchase Order CSOSValidated Purchase Order EDIFACT DESADV Despatch Advice Advance Ship Notice Warehouse Shipping Order Warehouse Shipping Advice Warehouse Stock Transfer Shipment Advice X12830 Planning Schedule Forecast Plan Forecast Plan Response Planned Order This issue has been resolved Multienterprise Process Link version 202540M1 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 CMCP41171 Class Loading Failure in B2B Maps Causes Transaction Errors API Several B2B maps failed with a "javalangClassNotFoundException" 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 PreRelease Transform Names B2BEDIX12852ProductActivityOBV3 B2BEDIX12867ProductTransferResaleReportOBV2 B2BTLXMLAdvanceShipNoticeIBV2 B2BIDocSHPORDDELVRY03ShipOrderIBV3 B2BIDocINVRPTINVRPT01InventoryBalanceIBV3 B2BEDIX12852ProductActivityIBV4 B2BEDIX12844ProductTransferAccountAdjustmentRequestOBV2 MPCSTEEPCISExtensionsSerializedShipmentNotice12IBV2 B2BEDIEDIFACTORDERSPurchaseOrderOBV6 B2BIDocSHPCONDELVRY07ShipAdviceIBV3 MPCSTEEPCISSerializedShipmentNotice12IBV7 B2BEDIEDIFACTORDRSPPurchaseOrderAcknowledgmentOBV3 MPCSTEEPCISSerializedShipmentNotice12OBV8 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 202540 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 CMCP39423 Missing LineLevel Fields in WSO Canonical Schema API The Warehouse Shipping Order (WSO) canonical schema was missing several important linelevel 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 linelevel fields ensuring data completeness and schema alignment across related processes This issue has been resolved CMCP39877 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 CMCP40080 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 CMCP40619 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 CMCP40873 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 CMCP41053 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 Receivedunder the "orderStatusCode" attribute in "orderItemStatusReport" The schema is updated to include the missing enumerations to support more complete reporting This issue has been resolved CMCP41073 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 TL86472 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 reexecute 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 TL88034 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 202542 There are no known issues in this release Multienterprise Process Link version 202541M1 There are no known issues in this release Multienterprise Process Link version 202541 There are no known issues in this release Multienterprise Process Link version 202540M2 There are no known issues in this release Multienterprise Process Link version 202540M1 There are no known issues in this release Multienterprise Process Link version 202540 There are no known issues in this release

Whats new in the Standard Link Actions version 202540

This document describes the TraceLink capabilities included in the Multienterprise Process Link Standard Link Actions version 202540 app release which is available on Validation on 11 Dec 2025 and Production on 10 Jan 2026

Whats new in Multienterprise Information Network Tower solution version 1600

Explore whats new in the Multienterprise Information Network Tower solution version 1600 release

FutureLink Mumbai 2026 Keynote Achieving Transformational Productivity Gains with Agentic Supply Chain Orchestration

Shabbir Dahod President & CEO of TraceLink outlines how agentic orchestration transforms endtoend supply chainsdigitizing transactions reducing manual work and driving measurable productivity inventory and revenue performance gains

TraceLink Leads in DSCSA Compliance as Deadline Approaches

TraceLink Named to RXinsider’s 2026 Pharmacy500 for Powering Digital Network Orchestration Across the Regulated Pharmacy Supply Chain

The recognition highlights TraceLink’s BusinesstoNetwork IntegrateOnce™ platform that enables endtoend digitalization interoperable compliance execution and operational resilience at industry scale

US Compounding Pharmacy Chooses MINT to Digitalize ProcuretoPay Transactions

Learn why a US compounding pharmacy chose TraceLink MINT to digitalize procuretopay accelerate transactions and support ontime payments across its supplier network

European Pharma Chooses MINT to Digitalize External Manufacturing Transactions

Discover why a European pharma company is leveraging MINT to digitalize external manufacturing transactions standardize forecast and PO exchange and improve ASN visibility with wholesalers

European Pharma Manufacturer Chooses MINT to Digitalize PO and ASN Exchange

Learn how a European pharma manufacturer plans to digitalize PO and ASN exchange across customers CMOs and 3PL partners

Navigate to help documentation support and community forum

Select the Help Center icon in the header to access the onestopshop help center for everything related to the network you are currently within (eg

Manage notifications

Apps send notifications when specific events happen and you receive these notifications within the OPUS user experience in the Notifications panel

TraceLink Builds on Transformative 2025 to Scale Agentic Orchestration Across the Global Life Sciences Supply Chain in 2026

As the life sciences industry enters 2026 navigating regulatory complexity global volatility and accelerating AI adoption TraceLink today reflects on a transformative 2025 and outlines its strategic priorities for scaling agentic orchestration across the global life sciences and healthcare supply chain

Configure TraceLink Extensible TraceLink Transfer

See the Administer Help Center for information about how to configure the B2B connections created in XTT AWS To configure B2B connections Application Administrators can create and view B2B connections which is a configured B2B gateway account that is uniquely identified by a B2B connection name using Applicability Statement 2 (AS2) protocols Secure File Transfer Protocol (SFTP) and Simple Mail Transfer Protocol (SMTP) in the XTT app After creating a B2B connection System Administrators can configure a B2B connection in the Administration app so the appropriate Link Identifier SAP Configuration and EDI Configuration settings can be used for the app or network System Administrators can add X12 EDIFACT or IDoc location settings information to complete adding a B2B connection System Administrators must configure an inbound or outbound message prior to adding the connection type information Assign Extensible TraceLink Transfer roles See the Administer Help Center for information about how to assign Extensible TraceLink Transfer roles to users Roles Application Administrator Allows users to create and update B2B connections and view B2B messages in the Extensible TraceLink Transfer app The Application Administrator in the Administration app can add users and assign their roles Member Standard Access Allows users to view existing B2B connections and the exchanged B2B messages Configurations for an SFTP connection Create a public and private key using PuTTYgen Open PuttyGen and select the RSA key type and set the number of bits to 4096 Copy the generated public key or select Save public key button Ensure the public key does not contain line feeds or carriage returns Enter a password in the Key passphrase field and confirm the updates Select Save private key button The generated public key is required while adding an SFTP connection Tips The recommended naming format for the public key is PublicKeytxt (eg USPT1VALPublicKeytxt) The recommended naming format for the private key is PrivateKeyppk Exchange files using FileZila or WinSCP See the information required to exchange documents using FileZila Open Site Manager and select New Site on Site Manager Fill in the following fieldsProtocol dropdown SFTPSSH File Transfer ProtocolHost Depending on whether the environment is val or prod the application hosts are Host (Valvir) valvirb2bsftpus1tracelinkcom Host (Valfkt) valfktb2bsftpeu1tracelinkcom Host (Prodvir) prodb2bsftpus1tracelinkcom Host (Prodfkt) prodfktb2bsftpeu1tracelinkcom Logon Type dropdown Key FileUser The user name provided while adding the SFTP connection in XTTKey File The path to the private key file saved using PuTTYgen Connect and enter the password as Key Passphrase (created during the creation of private key in PuTTYgen) to access the folder used for exchanging documents via the XTT SFTP connection See the information required to exchange documents using WinSCP Open WinSCP and fill in the following fieldsProtocol dropdown SFTPHost Depending on whether the environment is val or prod the application hosts are Host (Valvir) valvirb2bsftpus1tracelinkcom Host (Valfkt) valfktb2bsftpeu1tracelinkcom Host (Prodvir) prodb2bsftpus1tracelinkcom Host (Prodfkt) prodfktb2bsftpeu1tracelinkcom Select the Advanced button and select SSH > Authentication Navigate to the path of the private key file saved using PuTTYgen Enter the password as Key Passphrase (created during the creation of private key in PuTTYgen) to access the folder used for exchanging documents via the XTT SFTP connection Application Administrator require a public and private key to add an SFTP connection in XTT TraceLink recommends PuTTYgen app to create public and private key See FAQs for more information   Set up notifications Application Administrators can sign up to receive email notifications based on certain events See the Opus Platform Help Center for more information Notification settings Inbound Failure The user receives a notification when an error occurs for inbound B2B message Outbound Failure The user receives a notification when an error occurs for outbound B2B message

Ocean shipment booking confirmation transactions

The Ocean Shipment Booking Confirmation is a structured electronic transaction used to communicate the status of a shipment booking request between trading partners in the transportation and logistics industry

Ocean shipment booking confirmation (X12)

The Ocean Shipment Booking Confirmation is a structured electronic transaction used to communicate the status of a shipment booking request between trading partners in the transportation and logistics industry

Ocean shipment booking request transactions

The Ocean Shipment Booking Request also known as a Reservation Request is an electronic transaction used to initiate the process of securing transportation space with an ocean carrier freight forwarder or intermodal provider

Ocean shipment booking request (X12)

The Ocean Shipment Booking Request also known as a Reservation Request is an electronic transaction used to initiate the process of securing transportation space with an ocean carrier freight forwarder or intermodal provider

Ocean shipment status transactions

Ocean Shipment Status is an electronic message used by ocean carriers to provide shipment updates on the movement and handling of ocean freight shipments

Ocean shipment status (X12)

Ocean Shipment Status is an electronic message used by ocean carriers to provide shipment updates on the movement and handling of ocean freight shipments

Order status report transactions

Order Status Report is a key communication tool used to improve visibility and coordination across the supply chain

Organizational relationship transactions

The Organizational Relationships transaction is a master data message used to share structured information about organizational hierarchies relationships and identifiers between trading partners

Organizational relationship (X12)

The Organizational Relationships transaction is a master data message used to share structured information about organizational hierarchies relationships and identifiers between trading partners

Planned order transactions

A planned order is a systemgenerated proposal created within Enterprise Resource Planning (ERP) systemssuch as SAPor Advanced Planning Systems (APS) to signal the anticipated need to manufacture or procure a specific quantity of a pharmaceutical product or raw material at a specific time

Planned order (IDoc)

A planned order is a systemgenerated proposal created within Enterprise Resource Planning (ERP) systemssuch as SAPor Advanced Planning Systems (APS) to signal the anticipated need to manufacture or procure a specific quantity of a pharmaceutical product or raw material at a specific time

Price authorization acknowledgment (X12)

he price authorization acknowledgment transaction is used by manufacturers or suppliers to electronically communicate pricing decisions to distributors resellers or buying groups

Product activities transactions

The product activities report is routinely distributed to trading partners suppliers or upstream supply chain partners

Product activities (IDoc)

The product activities report is routinely distributed to trading partners suppliers or upstream supply chain partners

Purchase order acknowledgment transactions

Purchase orders allow companies to exchange data about requests to purchase goods and services with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record

Purchase order acknowledgments (IDoc)

Purchase orders allow companies to exchange data about requests to purchase goods and services with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record