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 13.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.1.0 app release, which is available on Validation on 13 Feb 2025 and Production on 27 Feb 2025.

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

Multienterprise Process Link, version 2025.1.0
Solutions supported by this app version:
- Multienterprise Information Network Tower, solution version 13.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 patches are released for this version:

Multienterprise Process Link, version 2025.1.3 is available on Validation on 27 Mar 2025 and Production on 13 Apr 2025.
Multienterprise Process Link, version 2025.1.2M1 is available on Validation and Production on 20 Mar 2025.
Multienterprise Process Link, version 2025.1.2 is available on Validation on 19 Feb 2025 and Production on 27 Feb 2025.
Multienterprise Process Link, version 2025.1.1 is available on Validation on 18 Feb 2025 and Production on 27 Feb 2025.

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

Revisions

Date	Revision	Description
30 Jan 2025	01	Initial version.
13 Feb 2025	02	The following updates have been made since the previous revision was distributed: 22 issues are added to Resolved issues. 0 issues are added to Known issues.
18 Feb 2025	03	The following updates have been made since the previous revision was distributed: Issue information for the Multienterprise Process Link, version 2025.1.1 patch is added: 1 issue is added to Resolved issues. 0 issues are added to Known issues.
19 Feb 2025	04	The following updates have been made since the previous revision was distributed: Issue information for the Multienterprise Process Link, version 2025.1.2 patch is added: 1 issue is added to Resolved issues. 0 issues are added to Known issues.
20 Mar 2025	05	The following updates have been made since the previous revision was distributed: Issue information for the Multienterprise Process Link, version 2025.1.2M1 patch is added: 7 issues are added to Resolved issues. 0 issues are added to Known issues.
27 Mar 2025	06	The following updates have been made since the previous revision was distributed: Issue information for the Multienterprise Process Link, version 2025.1.3 patch is added: 4 issues are added to Resolved issues. 0 issues are added to Known issues.
13 Apr 2025	07	The following update has been made since the previous revision was distributed: The Production date for version 2025.1.3 patch in Patch releases is updated to 13 Apr 2025.

API features

Multienterprise Process Link, version 2025.1.3

There is no new or updated API functionality included in this release.

Multienterprise Process Link, version 2025.1.2M1

There is no new or updated API functionality included in this release.

Multienterprise Process Link, version 2025.1.2

There is no new or updated API functionality included in this release.

Multienterprise Process Link, version 2025.1.1

There is no new or updated API functionality included in this release.

Multienterprise Process Link, version 2025.1.0

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

Send and Receive Carrier Shipment Statuses in X12 Format

Companies that own or link to Multienterprise Process Link can exchange carrier shipment statuses with their Partners via TraceLink in X12 format. Carrier shipment statuses ensure real-time visibility into the progress of a shipment as it moves through the supply chain, enabling stakeholders to monitor delivery schedules, address potential delays, and maintain high service levels. Exchanging carrier shipment statuses asynchronously via Multienterprise Process Link improves visibility into the progress of a shipment and enables the shipper to manage inventory proactively, coordinate resources, and adjust operations based on accurate shipment statuses and timelines.

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

The following new messages are available for sending or receiving carrier shipment statuses in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_214_CarrierShipmentStatus_IB_V1
- B2B_EDI_X12_214_CarrierShipmentStatus_OB_V1

Impact analysis

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

Send and Receive Routing and Carrier Instructions in X12 Format

Companies that own or link to Multienterprise Process Link can exchange routing and carrier instructions with their Partners via TraceLink in X12 format. Routing and carrier instructions are essential in transportation and shipping, providing a clear way for shippers, manufacturers, and others to share specific shipping instructions with logistics partners, carriers, and freight forwarders. Routing and carrier instructions help ensure goods are shipped according to the manufacturers preferences, requirements, and compliance rules. Manufacturers can exchange routing and carrier instructions asynchronously via Multienterprise Process Link with their upstream suppliers to communicate on which carriers to use for shipping to their facilities.

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

The following new messages are available for sending or receiving routing and carrier instructions in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_853_RoutingCarrierInstruction_IB_V1
- B2B_EDI_X12_853_RoutingCarrierInstruction_OB_V1

Impact analysis

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

Send and Receive Receiving Advice Acceptances in X12 Format

Companies that own or link to Multienterprise Process Link can exchange receiving advice acceptances with their Partners via TraceLink in X12 format. Receiving advice acceptances streamline goods transportation between entities to verify and manage delivery details efficiently. Exchanging receiving advice acceptances asynchronously via Multienterprise Process Link allows the buyer to confirm the receipt of goods or materials from the supplier, and acknowledge that the items have been delivered, inspected, and accepted in accordance with the order details.

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

The following new messages are available for sending or receiving receiving advice acceptances in this release:

X12 (inbound and outbound):
- B2B_EDI_X12_861_ReceivingAdvice_IB_V1
- B2B_EDI_X12_861_ReceivingAdvice_OB_V1

Impact analysis

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

Send and Receive Transactions via Email Messages in IDoc Format

The email messages feature has be improved to enable companies that own MINT and XTT and their Partners to exchange both inbound and outbound B2B messages via email by creating a SMTP connection in XTT. This update enables Owners and Partners receiving an outbound email to reply with an attachment.

This enhancement is particularly beneficial for Partners who do not own Multienterprise Information Network Tower (MINT), enabling them to exchange key business documents such as purchase orders (POs) and purchase order acknowledgments (PO Acks) MINT transactions, through standard email.

For example, companies who own MINT and XTT can send an email via the SMTP XTT connection, that triggers a MINT transaction (e.g., a purchase order) as an attachment to a Partner. After receiving the purchase order, the partner can reply to the email with the purchase order acknowledgment, which is then seamlessly recorded in the Owner’s MINT system. Throughout the process, documents are seamlessly converted into formats for both the Owner's and Partner's systems, ensuring smooth, efficient exchanges and supporting compatibility across platforms.

For detailed information about creating a SMTP connection in XTT for email, see Add an SMTP B2B connection.

Impact analysis

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

System features

Multienterprise Process Link, version 2025.1.3

There is no new or updated system functionality included in this release.

Multienterprise Process Link, version 2025.1.2M1

There is no new or updated system functionality included in this release.

Multienterprise Process Link, version 2025.1.2

There is no new or updated system functionality included in this release.

Multienterprise Process Link, version 2025.1.1

There is no new or updated system functionality included in this release.

Multienterprise Process Link, version 2025.1.0

The following new or updated system functionality is included in this release.These features are changes to the app to support another feature and do not have any impacts on their own.

Support for File Download Functionality in the Web UI

This feature includes updates to TraceLink's internal APIs that are leveraged by the UI to deliver the Base Transaction Object and Serialization Traceability Object feature in the Multienterprise Information Network Tower, solution version 13.0.0 solution release.

Impact analysis

The impacts for this feature are the same as the Base Transaction Object and Serialization Traceability Object feature in the Multienterprise Information Network Tower, solution version 13.0.0 solution release."

Stabilization and Usability Enhancements

This feature includes updates to TraceLink's internal APIs to improve the stability and usability of the Multienterprise Process Link application.

The enumerations EUDR - Due Diligence Reference Number (EUDR - DDR) and EUDR - Due Diligence Verification Number (EUDR - DDV) in referenceTransactionsTypeDefinition and b2bTransactionIdentifierReferenceTypeDefinition are updated for EUDR requirements.
The ORD-GQL request query handler is updated to support includeFields.
The following enhancements are made to the ASN subtypes:
- The containerIdentifier attribute is added in subtypes and indexed.
- PACKINGLIST and AIRWAYBILL enumeration values have been added to the b2bTransactionIdentifierType attribute.
- COMPLETED, CREATED, IN_PROGRESS, CANCELLED enumeration values have been added to the deliveryStatus attribute.
- The Indexes were added for BusinessName attribute related to Supplier , Customer , Ship from Location, Ship To Location in the corresponding subtypes.
The Inventory Updates maps are updated to include features required for customer implementations.
- IDoc (inbound and outbound):
  - B2B_IDoc_MBGMCR_MBGMCR03_InventoryUpdate_IB_V2
  - B2B_IDoc_MBGMCR_MBGMCR03_InventoryUpdate_OB_V3

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:
- API
Business segment impacts:
- All business segments for both Owners and Partners

Resolved issues

Multienterprise Process Link, version 2025.1.3

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-38378: Missing Fields in View/Edit Screen for Serialized Ship Notices	API	Total Quantity Shipped, Quantity, Unit of Measure, and Lot Number fields were missing in the View/Edit Serialized Ship Notices screen, despite being included in the input file. This issue has been resolved.
CMCP-38581: Transform Configuration Failed with an Error	API	An error occurs while configuring the B2B_EDI_X12_850_PurchaseOrder_IB_V6 transform. This issue has been resolved.
TL-66729:Duplicate PONumber Entry in Outbound Canonical	API	The Purchase Order Acknowledgment JSLT map has a duplicate entry of PONumber in `transactionReferenceIdentifierList` attribute. This issue has been resolved.
TL-66882: Missing Attributes and Enumeration Values in Canonical Schema Data Models	API	Attributes and enumeration values were missing in the canonical schema data models of Purchase Order, Inventory Balance, Advance Shipment Notices, and Forecast Plan and Response transactions. This issue has been resolved.

Multienterprise Process Link, version 2025.1.2M1

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-38079: EPCIS Inbound Serialized Shipment Notice Map Ignores the Extension Elements Section	API	TTS inbound receipt fails to capture extension element values from EPCIS Serialized Shipment Notice transaction. This issue has been resolved.
CMCP-38594: Added Support for WMMBID01 IDoc in Inventory Update	API	The standard transform support for WMMBID01 IDoc is missing in the Inventory Update transaction. Pre-Release Transform Name: B2B_IDoc_WMMBID_WMMBID01_InventoryUpdate_OB_V1. This issue has been resolved.
CMCP-38564: Update EDIFACT ASN Inbound and Outbound Formats	API	The transform functionality is missing a required date and time format, resulting in errors when processing packaging levels, as the Advance Shipment Notice includes a packing aggregation. This issue has been resolved.
CMCP-38608: Errors Occurred Due to Missing Packaging Aggregation in Input File	API	Errors occurred when packaging aggregation was missing in the input file of the inbound IDoc map of Advance Shipment Notice transaction. Pre-Release Transform Name: B2B_IDoc_DELVRY07_ASN_IB_V4. This issue has been resolved.
CMCP-38631: Missing Mapping for Segment E1EDK01/BELNR	API	The mapping for `E1EDK01/BELNR` is missing in the inbound IDoc map for Purchase Order Acknowledgment transaction. Pre-Release Transform Name: B2B_IDoc_ORDERS05_PurchaseOrderAcknowledgment_IB_V4. This issue has been resolved.
CMCP-38643: Missing Fields in GS and GE Segments	API	A validation error occurs due to the missing fields in GS & GE segment in X12 Purchase Order Acknowledgment transaction. Pre-Release Transform Name: B2B_EDI_X12_855_PurchaseOrderAcknowledgment_OB_V5. This issue has been resolved.
CMCP-38646:Errors in N1 Segment for Name, City, State, and Country	API	The outbound transform for purchase orders encountered errors in the N1 segments related to the Name, City, State, and Country elements. Pre-Release Transform Name: B2B_EDI_X12_850_PurchaseOrder_OB_V6. This issue has been resolved.

Multienterprise Process Link, version 2025.1.2

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

ID	Interface	Issue Description
CMCP-38574: Transaction Failure Between Owner Location and Partner Company	API	A transaction from the Owner location to the Partner company is failing due to a missing partner configuration for `b2bConnectionId`. This issue has been resolved.

CMCP-38574: Transaction Failure Between Owner Location and Partner Company

API

A transaction from the Owner location to the Partner company is failing due to a missing partner configuration for b2bConnectionId.

This issue has been resolved.

Multienterprise Process Link, version 2025.1.1

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
CMCP-38560: Access Denied Error for Integration Principal	API	The B2B transaction for Forecast Plan Response inbound transaction (from Partner to company location) fails with an access denied error due to insufficient permissions. This issue has been resolved.

Interface

Issue Description

CMCP-38560: Access Denied Error for Integration Principal

API

The B2B transaction for Forecast Plan Response inbound transaction (from Partner to company location) fails with an access denied error due to insufficient permissions.

This issue has been resolved.

Multienterprise Process Link, version 2025.1.0

The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.

ID	Interface	Issue Description
TL-59624: Forecast Plan Line Item Count Not Populated	API	The `lineItemCount` attribute on the Forecast Plan Search screen is not populated because the `lineItem` attribute is not being indexed. This issue has been resolved.
TL-59857: Missing Index in Line Item Count for Warehouse Ship Order	API	The LineItem is not visible on Warehouse Ship Order Search screen because the `lineItem` attribute is not indexed. This issue has been resolved.
TL-61523: Invoice Date Missing in Output File	API	Invoice Date is not populated in outbound JSLT map. This issue has been resolved.
TL-61650:PO Transaction Failure Due to JSLT Map Issue	API	The Purchase Order JSLT map is incorrectly converting null values to numbers. This issue has been resolved.
TL-61670: Result Code and Error Not Displayed on Error Panel	API	During outbound failures, the result code and error details are not displayed in the UX view panel. This issue has been resolved.
TL-61932: EPCIS Extension Elements Ignored for STE Transactions	API	MINT Outbound JSLT maps are missing to map elements in the outbound canonical. This issue has been resolved.
TL-62064: Validation Failure in ASN Subtype	API	The IB Contivo Map for IDoc accepts a `packagingLevel` input as a single character without converting it to a predefined enumeration in the canonical. As a result, the canonical saves the single-character input as is, leading to a validation failure in ASN subtype. This issue has been resolved.
TL-62247: Redeliver Functionality Not Enabled for Serialized Shipment Notices Transactions	API	Users were unable to redeliver an existing Serialized Shipment Notices transaction in the Web UI. This issue has been resolved.
TL-62511: Transaction Failing in Preparing to Send State for Partner	API	The quantityType field with code `10 (SCRAPPED)` is failing for the Partner while transitioning from Preparing to Send state for the Service-to-Service flow. This issue has been resolved.
TL-62723: Updated Canonical by Adding thirdPartyLogisticsInformation Attribute for Logistics Transactions and Subtypes	API	The canonical header is missing the `thirdPartyLogisticsInformation` attribute that stores provider information in the BTO subtype object for Shipping Order, Shipping Advice, Stock Transfer Shipment Advice, and Stock Transfer Receiving Advice transactions. This issue has been resolved.
CMCP-37832: Copy INTO Functionality Not Working for Forecast Plan	API	Unable to create Forecast Plan Response using Copy INTO button on the Forecast Plan View screen in Web UI. This issue has been resolved.
CMCP-37925: Missing Movement Types in Canonical Schema for Inventory Updates	API	Attribute `inventoryStatusUpdateCode` in canonical object type `canonicalInventoryUpdate` is missing in the inventory update canonical. This issue has been resolved.
CMCP-37954: Failures While Processing Shipment Mapping File	API	The `executeTransformToBytes` function encountered a failure while processing the transformation for the mapping file MPC_STE_JSON_Compliance_ReportSalesShipment_IB_V4. This issue has been resolved.
CMCP-38069: Missing Element in PO IDoc Maps	API	The `<E1EDKA1 SEGMENT=”1”> <PARVW>EN</PARVW>` field is missing from the inbound and outbound IDoc maps for Purchase Order. This issue has been resolved.
CMCP-38184: Missing Enumeration Values in ASN	API	The CANCELLED enumeration value is missing for deliveryStatus in Advance Shipment Notices transaction. This issue has been resolved.
CMCP-38291: JSLT Mapping Failure for Forecast Inbound Transactions	API	The Forecast Plan inbound JSLT maps is unable to convert string to integer for an attribute. This issue has been resolved.
CMCP-38344: Enumerations Not Indexed in ASN Reports and Dashboard	API	AIRWAYBILL enumertaion is missing from `referenceTransactionIdentifierList` attribute, and `containerIdentifier` attribute is missing from CONTAINER_NO for the Advance Shipment Notices canonical schema and subtypes. This issue has been resolved.
CMCP-38354: Missing Enumeration Value in b2bTransactionIdentifierType Attribute in ASN	API	The PACKINGLIST enumeration value is missing from the `b2bTransactionIdentifierType` attribute in the Advance Shipment Notices transaction. This issue has been resolved.
CMCP-38382: Missing Enumeration Values in ASN for DeliveryStatus in canonical	API	Missing CREATED, IN_PROGRESS and COMPLETED deliveryStatus in Advance Shipment Notices canonical. This issue has been resolved.
CMCP-38395: Multiple Outbound MINT Transactions Sent to the Same networkNode	API	Multiple transactions are being created in MINT but are all delivered to the same `networkNode` ID. This issue has been resolved.
CMCP-38401: Missing Indexes for BusinessName Attribute	API	The indexes are missing for `BusinessName` attribute related to Supplier , Customer , Ship from Location, Ship To Location in the corresponding subtypes. This issue has been resolved.
CMCP-38428: File Stuck in Inbound Processing State for Forecast Plan Response	API	The Forecast Plan Response subtypes are not supporting decimal values for `quantity` attribute. This issue has been resolved.