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 18.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.2.0 app release, which is available on Validation on 09 Jun 2026 and Production on 21 Jun 2026.

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

  • Multienterprise Process Link, version 2026.2.0

    Solutions supported by this app version:

    • Multienterprise Information Network Tower, solution version 18.0.0

The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).

Download the PDF

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

Patch releases

The following patch is released for this version:

  • Multienterprise Process Link, version 2026.2.0M1 is available on Validation and Production on 25 June 2026.

These patches are cumulative, and the most recent patch release includes functionality from all previous versions.

Revisions

Date Revision Description
21 May 2026 01 Initial version.
04 Jun 2026 02 The following updates have been made since the previous revision was distributed:
25 June 2026 03 The following updates have been made since the previous revision was distributed:
  • Issue information for the Multienterprise Process Link, version 2026.2.0M1 patch is added:

API features

Multienterprise Process Link, version 2026.2.0

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

Send and Receive Certificates Of Analysis in XML Format

Companies that own or link to Multienterprise Process Link can exchange Certificates Of Analysis with their Partners via TraceLink in XML format. Certificates of Analysis (CoA) enable suppliers to send structured quality test results to customers to confirm that materials meet agreed specifications. This feature helps customers verify product compliance, automate quality validation, and support efficient goods receipt, release, and traceability.

Exchanging Certificates Of Analysis asynchronously via Multienterprise Process Link allow systems to automatically validate results. Previously, customers reviewed paper or PDF certificates manually, which delayed release and increased the risk of errors.

Sending and receiving Certificates Of Analysis asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Certificates Of Analysis messages.

  • Leverage a record of Certificate of Analysis details for business or compliance purposes.

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

The following new messages are available for sending or receiving Certificates Of Analysis in this release:

  • XML (inbound and outbound):
    • B2B_XML_E55_CertificateOfAnalysis_IB_V1

    • B2B_XML_E55_CertificateOfAnalysis_OB_V1

Impact analysis

  • Interface options:

      API

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

Send and Receive Grocery Products Purchase Orders in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Grocery Products Purchase Orders with their Partners via TraceLink in X12 format. Grocery Products Purchase Orders enable retailers, wholesale distributors, and stores to send purchase orders to suppliers for finished consumer goods. This feature improves ordering accuracy, streamlines delivery coordination, and supports efficient, high-volume supply chain operations.

Exchanging Grocery Products Purchase Orders messages asynchronously via Multienterprise Process Link ensures timely and accurate order processing. Previously, retailers and distributors managed orders through manual documents or offline communication, which increased errors and delayed fulfillment.

Sending and receiving grocery products purchase orders asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Grocery Products Purchase Order messages.

  • Access a record of the Grocery Products Purchase Order message for business or compliance purposes.

  • Retrieve the input, output, and canonical files for a specific Grocery Products Purchase Order 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 Grocery Products Purchase Orders in this release:

  • X12 (inbound and outbound):
    • B2B_EDI_X12_875_GroceryProductsPurchaseOrder_IB_V1

    • B2B_EDI_X12_875_GroceryProductsPurchaseOrder_OB_V1

Impact analysis

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

Send and Receive Grocery Products Invoices in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Grocery Products Invoices with their Partners via TraceLink in X12 format. Grocery Products Invoices allow grocery suppliers to send invoices to retailers, wholesale distributors, and distribution centers after goods are delivered. This feature helps suppliers automate accounts payable reconciliation, reduce pricing discrepancies, and improve cash flow visibility.

Exchanging Grocery Products Invoices asynchronously via Multienterprise Process Link supports accurate three-way matching with purchase orders and advance ship notices. Previously, suppliers entered invoices manually and reconciled documents offline, which increased processing time and errors.

Sending and receiving grocery products invoices asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Grocery Products Invoices messages.

  • Leverage a record of Grocery Products Invoices details for business or compliance purposes.

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

The following new messages are available for sending or receiving Grocery Products Invoices in this release:

  • X12 (inbound and outbound):
    • B2B_EDI_X12_880_GroceryProductsInvoice_IB_V1
    • B2B_EDI_X12_880_GroceryProductsInvoice_OB_V1

Impact analysis

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

Send and Receive Motor Carrier Load Tenders in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Motor Carrier Load Tenders with their Partners via TraceLink in X12 format. Motor Carrier Load Tenders enable shippers and third-party logistics providers (3PL) to offer shipments to motor carriers for transportation. This feature improves load visibility, reduces manual data entry, and accelerates carrier confirmation. The Motor Carrier Load Tender includes required shipment and routing details to support carrier evaluation and response.

Exchanging Motor Carrier Load Tenders asynchronously via Multienterprise Process Link automates load creation and carrier communication within Transportation Management Systems (TMS). Previously, shippers communicated shipment offers through manual email, phone calls, or disconnected systems, which delayed carrier confirmation and increased errors.

Sending and receiving Motor Carrier Load Tenders asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Motor Carrier Load Tenders.

  • Access a record of the Motor Carrier Load Tenders for business or compliance purposes.

  • Retrieve the input, output, and canonical files for a specific Motor Carrier Load Tender 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 Load Tenders in this release:

  • X12 (inbound and outbound):
    • B2B_EDI_X12_204_MotorCarrierLoadTender_IB_V1
    • B2B_EDI_X12_204_MotorCarrierLoadTender_OB_V1

Impact analysis

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

Send and Receive Load Tender Responses in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Load Tender Responses with their Partners via TraceLink in X12 format. Load Tender Responses enable motor carriers to respond to shipment offers from shippers, brokers, or third-party logistics providers (3PL). This feature improves transportation visibility, reduces manual follow-up, and streamlines coordination across supply chain operations.

Exchanging Load Tender Responses asynchronously via Multienterprise Process Link indicates whether a shipment is accepted, declined, or accepted with conditions. The response references the original EDI 204 Motor Carrier Load Tender to confirm transportation capacity and execution details.

Previously, carriers confirmed shipment offers through manual email, phone calls, or disconnected systems, which delayed confirmation and increased errors.

Sending and receiving Load Tender Responses asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshootLoad Tender Responses.

  • Access a record of the Load Tender Responses for business or compliance purposes.

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

The following new messages are available for sending or receiving Load Tender Responses in this release:

  • X12 (inbound and outbound):
    • B2B_EDI_X12_990_LoadTenderResponse_IB_V1

    • B2B_EDI_X12_990_LoadTenderResponse_OB_V1

Impact analysis

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

Send and Receive Ocean Bill Of Ladings in EDIFACT and X12 Formats

Companies that own or link to Multienterprise Process Link can exchange Ocean Bill Of Ladings with their Partners via TraceLink in EDIFACT and X12 formats. Ocean Bill of Ladings enable ocean carriers or their agents to send bill of lading data to shippers and other authorized parties for international maritime shipments. This feature improves shipment visibility, supports customs clearance and trade compliance, and reduces documentation disputes.

Exchanging Ocean Bill Of Ladings asynchronously via Multienterprise Process Link provides a formal record of goods, confirm contract terms, and support transfer of title when required.

Sending and receiving Ocean Bill Of Ladings asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Ocean Bill Of Ladings.

  • Access a record of the Ocean Bill Of Ladings for business or compliance purposes.

  • Retrieve the input, output, and canonical files for a specific Ocean Bill 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 Ocean Bill Of Ladings in this release:

  • EDIFACT (outbound):
    • B2B_EDI_EDIFACT_IFTMCS_OceanBillOfLading_OB_V1
  • X12 (inbound):
    • B2B_EDI_X12_310_OceanBillOfLading_IB_V1

Impact analysis

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

Send and Receive Purchase Order Change Requests in X12 Format

Companies that own or link to Multienterprise Process Link can exchange Purchase Order Change Requests with their Partners via TraceLink in X12 format. Purchase Order Change Requests enable buyers to send updates to previously submitted purchase orders. This feature helps buyers and suppliers maintain accurate order details, reduce fulfillment errors, and stay aligned on order changes. After receiving the request, the supplier may respond with a Purchase Order Acknowledgment with Change to confirm acceptance or rejection of the updates.

Exchanging Purchase Order Change Requests asynchronously via Multienterprise Process Link enables updates to quantities, pricing, delivery dates, or line items.

Sending and receiving Purchase Order Change Requests asynchronously through Multienterprise Process Link enables companies and their Partners to:

  • Search for, view, and troubleshoot Purchase Order Change Requests.

  • Access a record of the Purchase Order Change Requests for business or compliance purposes.

  • Retrieve the input, output, and canonical files for a specific Purchase Order Change 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 Purchase Order Change Requests in this release:

  • X12 (inbound and outbound):
    • B2B_EDI_X12_860_PurchaseOrderChangeRequest_IB_V1

    • B2B_EDI_X12_860_PurchaseOrderChangeRequest_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.2.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.

Standard Picklist: Dynamic Data Integration

This release introduces the Standard Picklist component, which dynamically populates drop-down options from a centralized data source. This feature improves data consistency, reduces manual maintenance, and ensures selection from the most current reference data. The Standard Picklist retrieves values through a GraphQL query from a centrally managed catalog or Reference Data Manager, supporting large and frequently updated datasets without manual form updates.

Previously, administrators configured static picklists that required manual updates whenever source data changed, which increased.

Impact analysis

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

Standard Reports in Operational Messages Orchestration

Companies that own Multienterprise Process Link and their Partners can use standard reporting across Operational Messages orchestrations. This enhancement supports both existing and future transactions, ensuring each orchestration has baseline visibility and access to scalable, actionable analytics. As operational messages become increasingly complex and data-driven, the need for consistent and reliable access to transaction-level insights becomes more important than ever.

This feature also includes additional base and joint reports for External Manufacturing, Commerce, and Transportation orchestrations.

Impact analysis

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

Stabilization and usability enhancements

  • Enhanced the invoice canonical schema to address gaps identified during gap analysis, ensuring more complete data coverage, improved alignment with business requirements, and better support for downstream processing and integrations.

  • Enhanced the Standard Transform for Purchase Order (EDI ANSI X12 850) to support mapping across multiple segments and enumerations, improving flexibility and accuracy in data transformation. This update ensures better alignment with diverse partner requirements, enables consistent handling of complex data structures, and strengthens support for scalable and maintainable integrations.

  • Enhanced the canonical data models to address gaps caused by missing enumerations in quantityType, ensuring more complete value coverage and improved data consistency. This update enhances validation, aligns the model with business and transaction requirements, and supports more accurate and reliable data transformations across integrations.

This feature also includes minor updates to improve the stability of the Multienterprise Information Network Tower solution and its ability to communicate with other TraceLink apps and solutions.

Impact analysis

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

Resolved issues

Multienterprise Process Link, version 2026.2.0M1

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-40993: Failure Caused by Invalid Date Value Processing in WSTRA API

The inbound Warehouse Stock Transfer Receipt Advice EDIFACT map was failing with the error "Unparseable date: '--T'". The map was generating a RECEIVED date type (DTM 1.1 = 310) with an invalid date value of "--T", even when the source EDIFACT message did not contain a DTM+310 segment.

To fix this issue, the transform logic is updated to validate the presence of the source date field before generating and processing the "RECEIVED" date.

Pre-Release Transform Name:

  • B2B_EDI_EDIFACT_RECADV_WHS_StockTransferReceiptAdvice_IB_V1

This issue has been resolved.
CMCP-41394: Processing Acknowledgment Map Failure API

The inbound Processing Acknowledgment X12 transactions were failing during processing with the error "Valid error code value in source AK502 is required", even when AK502 contained the valid value "5". As a result, identical files could sometimes process successfully and sometimes fail.

To fix this issue, the transform is created eliminating the cache inconsistency and ensuring consistent processing.

Pre-Release Transform Name:

  • B2B_EDI_X12_997_ProcessingAcknowledgment_IB_V4

This issue has been resolved.
CMCP-41911: Missing Support for Outbound EDI X12 Remittance Advice API

An outbound Remittance Advice X12 mapping capability was not available, preventing the electronic transmission of remittance advice transactions to an external partner system. Although a standard inbound map existed, the absence of an outbound map created a gap in the end-to-end remittance advice process.

To fix this issue, the transform is created to support outbound remittance advice transactions.

Pre-Release Transform Name:

  • B2B_EDI_X12_820_RemittanceAdvice_OB_V1

This issue has been resolved.
CMCP-41912:Missing Support for Outbound EDI X12 180 Return Authorization Request API

An outbound Return Authorization Request X12 mapping capability was not available, preventing the electronic transmission of return authorization transactions to an external partner system. While a standard inbound X12 180 map and an outbound IDoc map were already available, the absence of an outbound X12 map created a gap in supporting end-to-end return authorization processing.

To resolve the issue, the transform is developed to support outbound X12 Return Authorization Request transactions.

Pre-Release Transform Name

  • B2B_EDI_X12_180_ReturnAuthorizationRequest_OB_V1

This issue has been resolved.
CMCP-42413:Missing Support for Outbound IDoc WMMBID02 Inventory Update API

The Inventory Update transactions could only be generated in the WMMBID01 IDoc format, preventing support for partners that required the newer WMMBID02 IDoc format. Since WMMBID02 includes additional data elements not available in WMMBID01, such as "receiving/issue storage location (E1MBXYI/UMLGO)" and "receiving/issue batch (E1MBXYI/UMCHA)", the existing solution could not meet the required transaction format and data requirements.

To resolve the issue, the transform is created to support the WMMBID02 IDoc format and its additional fields. The Inventory Update schema (V10) is enhanced by adding the "destinationStorageLocation" and "receivingIssuingLotNumber" elements.

Pre-Release Transform Name

  • B2B_IDoc_WMMBXY_WMMBID02_InventoryUpdate_OB_V1

This issue has been resolved.
CMCP-42641: Failure Caused by DTM Qualifier 804 in Purchase Order API

The inbound Purchase Order EDIFACT transform was failing when processing Purchase Order transactions containing the PAT-DTM segment DTM+12:60:804. The map incorrectly attempted to parse the value "60" as a date in YYYY-MM-DD format, resulting in a "TFormatDataException".

To resolve the issue, the transform is updated to correctly map "DTM01.2" to "discountDueNumberOfDays" whenever "DTM01.3 = 804". For all other "DTM01.3" qualifiers, the existing behavior of mapping to "discountDueDate" is retained.

Pre-Release Transform Name

  • B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_IB_V6

This issue has been resolved.
CMCP-42643:Invalid N104 Data Handling in Product Transfer Account Adjustment Response API

The outbound Product Transfer Account Adjustment Response X12 transform was generating invalid transactions when the source data contained an "N104" value shorter than the minimum X12-required length of two characters. The map omitted the "N104" element while still populating the corresponding qualifier in "N103", resulting in an invalid X12 output structure.

To resolve the issue, the transform is updated to validate the length of "N104" and throw an error whenever a value shorter than two characters is provided. This prevents the generation of invalid X12 transactions.

Pre-Release Transform Name

  • B2B_EDI_X12_849_ProductTransferAccountAdjustmentResponse_OB_V3

This issue has been resolved.
CMCP-42651: Failure Caused by Missing UoM in ASN API

The inbound Advance Ship Notice transform failed with a "TFormatDataException" because it required a Unit of Measure (VOLEH) even when the volume field "(VOLUM)" was populated with a value of "0".

To resolve the issue, the transform is updated to map "VOLUM "only when the field is present and greater than "0". UoM validation is now performed only when "VOLUM" contains a value greater than "0", preventing unnecessary validation errors when volume is not populated or is zero.

Pre-Release Transform Name

  • B2B_IDoc_DELVRY07_ZTLASN01_PT_ASN_IB_V2

This issue has been resolved.
CMCP-42663: Missing support for Inbound TRADACOMS Purchase Order API

Purchase Order transactions needed to be received in TRADACOMS (ANA standard) format, but TRADACOMS was not supported as a standard inbound format, with only EDIFACT and X12 available. This created a gap in processing inbound Purchase Orders using the required format.

To resolve the issue, a new map is created to support inbound Purchase Order transactions.

Pre-Release Transform Name

  • B2B_EDI_TRADACOMS_ORDERS_ANA_PurchaseOrder_IB_V1

This issue has been resolved.
CMCP-42695: Outbound ORDERS05 Purchase Order Failure for UNIT Pricing Type API

Pricing information from inbound X12 850 Purchase Order transactions was not being passed to the outbound ORDERS05 IDoc. The issue was caused by a "pricingType" mismatch, where the inbound transform populated "pricingType" as "UNIT", but the outbound ORDERS05 transform (V10) only accepted "NET", resulting in pricing conditions being dropped.

To resolve the issue, the transform is updated to accept both "UNIT" and "NET" as valid "pricingType" values, ensuring Unit Price information is correctly mapped.

Pre-Release Transform Name

  • B2B_IDoc_ORDERS05_PurchaseOrder_OB_V11

This issue has been resolved.
CMCP-42712: Order Status Report Mapping Failure for Hybrid UoM Codes and Organizational Qualifiers API

The inbound Order Status Report transactions were failing validation because they contained a hybrid mix of SAP and ISO Unit of Measure codes (for example, "LB" instead of the expected "LBR" for pounds) and organizational qualifier values (QUALF 012 and 019) that were not included in the supported code lists.

To resolve the issue, the transform is updated to support hybrid UoM codes and to ignore unsupported "E1EDK14" qualifier values instead of generating validation errors.

Pre-Release Transform Name

  • SAP_IDoc_ORDRSP_ORDERS05_OrderStatusReport_IB_V2

This issue has been resolved.
CMCP-42735: Missing Order Reason data in ORDERS05 Purchase Order Acknowledgment transactions API

The Purchase Order Acknowledgment transaction did not capture Order Reason information for manually created Purchase Orders because the inbound mapping did not populate the "E1EDK01/AUGRU" (Code of Order Reason) and "E1EDK01/AUGRU_BEZ" (Description of Order Reason) fields into the canonical model.

To resolve the issue, the transform is updated to map "E1EDK01/AUGRU" to "reasonForOrder" and "E1EDK01/AUGRU_BEZ" to "reasonDescription", ensuring Order Reason details are captured and available for downstream processing.

Pre-Release Transform Name

  • B2B_IDoc_ORDERS05_PurchaseOrderAcknowledgment_IB_V6

This issue has been resolved.
CMCP-42891: Missing Support for Mapping Line Level Tax Details in Invoice EDI X12 API

The inbound Invoice X12 transform did not support mapping of the line-level "TXI "(Tax) segment, preventing tax information from being captured and processed at the invoice line level.

To resolve the issue, the transform is updated to support mapping of the line-level TXI (Tax) segment, ensuring invoice tax details are correctly captured and made available.

Pre-Release Transform Name

  • B2B_EDI_X12_810_Invoice_IB_V8

This issue has been resolved.
CMCP-42895: Error in N102 field Purchase Order map for N101 = VN API

The inbound Purchase Order X12 transform generated an error when "N102" (Name) was missing and "N101=VN (Vendor)", despite treating "N102" as optional when "N101=SU (Supplier)". Since both "VN" and "SU" qualifiers map to "supplierBusinessInformation", this inconsistent validation behavior caused unnecessary transaction failures.

To resolve the issue, the transform is updated to treat "N102" as optional for both "N101=VN" and "N101=SU", ensuring consistent processing of supplier information and preventing errors when the Name field is not provided.

Pre-Release Transform Name

  • B2B_EDI_X12_850_PurchaseOrder_IB_V10

This issue has been resolved.
CMCP-42933: Error Caused by Incorrect N9 Segment Validation Logic in Purchase Order API

The inbound Purchase Order X12 transform generated an error when "N902" (Transaction Reference Identifier) was not populated in the "N9" segment, even when "N903" was present. The validation logic incorrectly required "N902" whenever "N901=L1", despite "N902" and "N903" being conditionally dependent under the X12 standard.

To resolve the issue, the transform is updated to correct the validation logic, making "N902" optional when "N903" is populated and "N901=L1". This aligns processing with the X12 standard and prevents unnecessary transaction failures.

Pre-Release Transform Name

  • B2B_EDI_X12_850_PurchaseOrder_IB_V10

This issue has been resolved.
CMCP-43065: Error Caused by Missing STATELOCAL tax type entry in Invoice API

Data validation error occurred in the outbound Invoice transform when processing canonical invoices containing the "taxType" value "STATELOCAL", because the value was not included in the permitted values list. This caused outbound processing to fail within the "IT1" segment loop.

To resolve the issue, the transform is updated by adding "STATELOCAL", enabling correct mapping of the value to the "TXI" segment.

Pre-Release Transform Name

  • B2B_EDI_X12_810_Invoice_OB_V7

This issue has been resolved.
CMCP-43132:Missing PAT Segment Support in Invoice API

The inbound Invoice transform, only supported the "PYT" payment terms segment, which were specific to the "D01B" EDIFACT standard. As a result, payment terms contained in the "PAT" segment used by the "D96A" standard were not processed.

To resolve the issue, the new transform now supports both the "PAT" segment (used in D96A) and the "PYT" segment (used in D01B), enabling payment terms to be processed consistently across EDIFACT versions.

Pre-Release Transform Name

  • B2B_EDI_EDIFACT_INVOIC_Invoice_IB_V4

This issue has been resolved.

Multienterprise Process Link, version 2026.2.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-39696:Purchase Order Acknowledgment Inbound Validation Failure for processingFunctionTypeCode Field API

An issue was identified where Purchase Order Acknowledgment (PO ACK) inbound transactions failed validation because certain "processingFunctionTypeCode" enumeration values were not supported during inbound processing.

To fix this issue, the transformation logic is updated to avoid direct mapping of the "processingFunctionTypeCode" field. Instead, the values are now handled through "customFields", enabling successful validation and processing of PO ACK transactions.

This issue has been resolved.
CMCP-41595: Unit Price Data Not Processed in Canonical During File Ingestion API

An issue was identified where Unit Price data provided in inbound files was not being processed in the canonical model. This occurred because the canonical logic was hard coded to support "pricingType = NET" only.

To fix this issue, the canonical logic is updated. Additional field enhancements and new field support are also introduced to improve pricing data processing flexibility across multiple use cases.

This issue has been resolved.
CMCP-42499: DG02 Identifiers Not Populated in MINT UI API

An issue was identified where DG02 identifiers were not being populated in the MINT UI due to missing subtype mapping from the canonical model.

To fix this issue, the MINT mappings are updated to populate the subtype value from the canonical data.

This issue has been resolved.
TL-104105: Purchase Order Transactions Remained in Processed Status in MINT API

An issue was identified where purchase order transactions in the MINT interface remained in a processed status and did not progress further, even though processing appeared successful. This issue occurred when required payment terms data was missing from inbound or outbound purchase order transaction records.

To resolve the issue, updates are made to improve transaction handling, and purchase orders now process successfully through the MINT interface.

This issue has been resolved.

Known issues

Multienterprise Process Link, version 2026.2.0M1

There are no known issues in this release.

Multienterprise Process Link, version 2026.2.0

There are no known issues in this release.

Tag end