Tracelink University
## Breadcrumb
1. [Home](/)
2. [Resources](/resources/resource-center)
3. [TraceLink University](/resources/tracelink-university)
# Multienterprise Information Network Tower FAQs
- [Download PDF](/node/632416/pdf)
- [Share](#)
- [ LinkedIn ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.tracelink.com/resources/tracelink-university/multienterprise-information-network-tower-faqs-0&title= Multienterprise Information Network Tower FAQs&summary=TraceLink apps are extended through solutions, which pull together assets that define how the app looks and functions when users interact with it (i.e. &source=TraceLink "LinkedIn")
- [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/multienterprise-information-network-tower-faqs-0&t= Multienterprise Information Network Tower FAQs "Facebook")
- [ Mail ](mailto:?subject= Multienterprise Information Network Tower FAQs+|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/multienterprise-information-network-tower-faqs-0 "Mail")
- [ Twitter ](https://twitter.com/intent/tweet?text= Multienterprise Information Network Tower FAQs https://www.tracelink.com/resources/tracelink-university/multienterprise-information-network-tower-faqs-0&via=TraceLink "Twitter")
#### Table of contents
## General
[What are solutions?](#)TraceLink apps are extended through **solutions**, which pull together assets that define how the app looks and functions when users interact with it (i.e. the app's data model, pages workflows, roles, and policies). Solutions available through the Marketplace Catalog can be saved and configured to meet a company's specific use cases and business needs.
[What solutions are available for Multienterprise Process Link?](#)The **Multienterprise Information Network Tower** solution allows companies to exchange notices for commercial activities that involve a change of ownership (e.g. shipments and invoices) while maintaining the data integrity and security of their system of record.
For companies operating in Brazil, the **Multienterprise Information Network Tower** solution allows them to exchange serialized notices for commercial activities that involve a change of ownership (e.g. shipments) while maintaining the data integrity and security of their serialized system of record (e.g. trade partners initiating serial number status updates that might trigger compliance reports, which could not be repaired in the TraceLink system). At this time, serialized sales shipment notices only are supported. These notices allow companies to comply with the recommendation of Brazil's ANVISA Law No. 13.410/2016.
[What do you mean by Canonical?](#)It is TraceLink's system data format that is irrelevant to the device or program's function. The canonical data model allows information to be exchanged with any partner on the network, regardless of their data format.
[How are Brazil shipment notices triggered? ](#)**If the Owner is sending the shipment to a Partner:**1. The Owner sends a sales shipment through Serialized Operations Manager with a Distribution Type of Sale - In Country and a Ship To Country of Brazil.
2. Brazil Compliance generates a Shipment report (if the appropriate event trigger is enabled). For more information about additional event trigger conditions that must be met for the report to generate, see the [Brazil Compliance Help Center](https://opus.tracelink.com/documentation/en-US/Content/top_nav/use_tracelink_apps.htm).
3. Multienterprise Process Link generates a shipment notice (if the appropriate event trigger is enabled) and sends the Multienterprise Process Link Serialized Shipment Notice - Brazil message to the receiving Partner.
**If a Partner is sending the shipment to the Owner:**
1. The Partner sends a Multienterprise Process Link Serialized Shipment Notice - Brazil message.
2. TraceLink processes the Multienterprise Process Link message and creates a corresponding sales shipment in Serialized Operations Manager.
[Which events are captured in the audit trail? ](#)The following Multienterprise Process Link events are captured in the Track & Trace Services audit trail:
| functionalArea | businessObjectType | action | Description |
|---|---|---|---|
| Info Exchange | Transaction - Multienterprise Process Connect - Serialized Shipment Notice - Brazil Inbound | Create | Captures when the company sends a Serialized Shipment Notice - Brazil Inbound message type in Multienterprise Process Connect, using EPCIS v1.2 or ANVISA format. |
| Info Exchange | Transaction - Multienterprise Process Connect - Serialized Shipment Notice - Brazil | Create | Captures when the company sends a Serialized Shipment Notice - Brazil message type in Multienterprise Process Connect, using EPCIS v1.2 or ANVISA format. |
## Roles
[](#)[What roles can be assigned to Multienterprise Process Link users?](#)For more information about the roles assigned to Multienterprise Process Link users, see Assign Multienterprise Process Link roles.
[How do roles provide users with access?](#)Roles group a set of permissions for specific actions (either in the UI or via API), side menu items, and data within an app. The solution applied to the app or its network determines which roles are available. Administrators assign users to roles when they assign users to an app, its network, or its Links.
Owners assign specific roles to Links, which allow their Partners to assign those roles to the Partner users with access to the Link.
[How do I add or edit roles?](#)Companies must own OPUS Solution Environment (OSE) to add or edit roles. If your company owns OSE and you also have the Solution Designer role assigned, you can add new roles to a Company Solution or edit existing roles by navigating to OSE and selecting Roles in the side menu. See the OPUS Solution Environment Help Center for more information. If your company does not own OSE, then contact TraceLink Support for more information.
## OPUS Platform
[What are the password requirements for TraceLink SSO?](#)Passwords must be a minimum of 8 characters, must *not* be your email, and must include at least one:
- Numerical digit
- Lowercase letter
- Uppercase letter
- Special character
If your company was enabled on the OPUS Platform from Track & Trace Services, the following password settings from Track & Trace Services apply:
- Number of previous passwords that cannot be reused.
- Number of login attempts allowed before the account is locked.
- Number of days until the password expires.
If your company was *not* originally enabled on Track & Trace Services, the following default settings apply to TraceLink SSO:
- The previous 6 passwords cannot be reused.
- 5 login attempts are allowed before the account is locked.
- Passwords expire in 30 days.
[Which browsers does the OPUS Platform support?](#)The (Undefined variable: app\_name.OPUS Platform) supports the following web browsers:
- **Google Chrome** (recommended): Versions 57, 68, 74, or above
- **Microsoft Edge**: Version 113 or aboveFor the most stable and optimized performance, use Google Chrome. When using Microsoft Edge, additional configuration may be required to ensure optimal performance. See the *My OPUS experience is slow in Microsoft Edge* in the *Troubleshoot a Problem* topic for Microsoft Edge-specific guidance.
- **Mozilla Firefox**: Versions 60, 63, 67, or above
- **Apple Safari**: Versions 12.1.2, 13.0, or above
The OPUS Platform supports the following mobile browsers:
- **Google Chrome Mobile**: Version 80.0 or above
- **Android Web View**: Version 80.0 or above
- **iOS Safari**: Version 13.1 or above
#### Table of contents
##### Related Content
[  ](/resources/tracelink-university/configure-tracelink-multienterprise-information-network-tower)
##### Configure TraceLink for Multienterprise Information Network Tower
Unlike other OPUS apps, Multienterprise Process Link must be configured on Track & Trace Services because Multienterprise Process Link supports asynchronous messages, which are not yet available on the OPUS.
[View More](/resources/tracelink-university/configure-tracelink-multienterprise-information-network-tower)
[  ](/resources/tracelink-university/troubleshoot-problem-multienterprise-information-network-tower)
##### Troubleshoot a problem in Multienterprise Information Network Tower
Administrators assign roles that limit users' access to different functions.
[View More](/resources/tracelink-university/troubleshoot-problem-multienterprise-information-network-tower)
[  ](/resources/tracelink-university/whats-new-multienterprise-information-network-tower-solution-1)
##### What's new in Multienterprise Information Network Tower, solution version 9.0
Explore what's new in the Multienterprise Information Network Tower, solution version 9.0 release.
[View More](/resources/tracelink-university/whats-new-multienterprise-information-network-tower-solution-1)
[  ](/resources/tracelink-university/whats-new-multienterprise-information-network-tower-solution-0)
##### What's new in Multienterprise Information Network Tower, solution version 11.0
Explore what's new in the Multienterprise Information Network Tower, solution version 11.0 release.
[View More](/resources/tracelink-university/whats-new-multienterprise-information-network-tower-solution-0)
[  ](/resources/tracelink-university/whats-new-multienterprise-process-link-version-20246)
##### What's new in Multienterprise Process Link, version 2024.6
To learn more about what's new in the Multienterprise Information Network Tower, solution version 11.0 that provides the user interface for this app, see
Release information This document describes the TraceLink capabilities included in the Multienterprise Process Link, version 2024.6 app release, which is available on Validation on 26 Sep 2024 and Production on 10 Oct 2024.
The following apps are impacted by this release and will be updated to the version listed:
Multienterprise Process Link, version 2024.6 Solutions supported by this app version:
Multienterprise Information Network Tower, solution version 11.0 The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).
These release notes are subject to change based on the successful 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 patches are released for this version:
Multienterprise Process Link, version 2024.6.0M1 is available on Validation on 01 Oct 2024 and Production on 10 Oct 2024. These patches are cumulative, and the most recent patch release includes functionality from all previous versions.
Revisions Date Revision Description 12 Sep 2024 01 Initial version. 26 Sep 2024 02 The following updates have been made since the previous revision was distributed:
The Send and Receive Geolocations in the Web UI and via B2B Message in GeoJSON Format is added to the release. The following transforms were removed from the Enhancements to Existing Messages feature:B2B_IDoc_INVOIC02_Invoice_OB_V2B2B_EDI_EDIFACT_INVOIC_Invoice_IB_V3B2B_EDI_EDIFACT_INVOIC_Invoice_OB_V2B2B_EDI_X12_810_Invoice_IB_V4B2B_EDI_X12_810_Invoice_OB_V2B2B_EDI_X12_830_ForecastPlan_IB_V3 0 issues are added to Resolved issues. 0 issues are added to Known issues. 01 Oct 2024 03 The following updates have been made since the previous revision was distributed:Issue information for the Multienterprise Process Connect, version 2024.6.0M1 patch is added: The Enhancements to Existing Invoice and Forecast Plan Messages feature is added. 1 issues are added to Resolved issues. 0 issues are added to Known issues. 01 Oct 2024 04 The following updates have been made since the previous revision was distributed:
The following transforms were removed from the Enhancements to Existing Invoice and Forecast Plan Messages feature:B2B_EDI_EDIFACT_INVOIC_Invoice_IB_V3B2B_EDI_EDIFACT_INVOIC_Invoice_OB_V2 API features Multienterprise Process Link, version 2024.6.0M1 The following new or updated API functionality is included in this release.
Enhancements to Existing Invoice and Forecast Plan Messages The invoice and forecast transforms are updated to improve how TraceLink maps certain elements within the transform and elements and enumerations are added to the transforms to record additional information customers may want to include. The following existing invoice and forecast plan message types have been updated and their transform versions incremented to the versions below:
Forecast transforms:B2B_EDI_X12_830_ForecastPlan_IB_V3 Invoice transforms:B2B_IDoc_INVOIC02_Invoice_OB_V2B2B_EDI_X12_810_Invoice_IB_V4B2B_EDI_X12_810_Invoice_OB_V Multienterprise Process Link, version 2024.6.0 The following new or updated API functionality is included in this release.
The Multienterprise Process Connect app is renamed to Multienterprise Process Link in version 2024.6.0. This change aligns the app name more closely with the business functionally that the app provides.
Update the Multienterprise Information Network Tower Solution and Multienterprise Process Link App to Leverage the Platform Capabilities Included with the OPUS Ensemble Release The Multienterprise Information Network Tower solution and Multienterprise Process Link application are updated in this release to leverage the capabilities and efficiencies included in the OPUS Ensemble release. These updates reduce the demands on back-end processing, allowing for the development of more powerful solutions and applications. As a result of these updates, the search screen for each business object is updated along with the Search B2B Messages screen, which is renamed to Search Business Transactions. Additionally, all existing functionality is preserved, but has been updated and reconfigured to integrate with the platform capabilities enabled by the OPUS Ensemble release.
Impact analysis
Interface options:Web UI API Business segment impacts:All business segments for both Owners and Partners. New Search Screen for Serialization Traceability Exchange (STE) Messages The new Search Serialization Transactions screen is available to view the status of and troubleshoot any transforms using the new STE object type (e.g. MPC\_STE\_EPCIS\_SerializedShipmentNotice\_1\_2\_IB) that is separate from the search screen for standard object types (e.g. B2B\_IDoc\_ORDERS05\_PurchaseOrder\_IB). Previously, all object types for B2B messages were available on the same search screen. For example, when customers exchange serialized shipment notice B2B messages via Multienterprise Process Link, users now search for them on a new screen different than the existing one they search for non-STE B2B messages (e.g. B2B\_IDoc\_ORDERS05\_PurchaseOrder\_IB) on. Giving STE messages their own search screen enables customers to quickly access the messages containing their serialization data without having to filter through a large volume of non serialization messages.
To enable the STE messages to have their own search screen, the back-end STE object type is updated to leverage the platform capabilities included with the OPUS Ensamble Release.
Impact analysis
Interface options: Web UI Business segment impacts:All business segments for both Owners and Partners Send and Receive Geolocations in the Web UI and via B2B Message in GeoJSON Format Companies can exchange geocoordinates with their customers using the Multienterprise Information Network Tower Web UI or via B2B message in GeoJSON format using Multienterprise Process Link. Exchanging geographic coordinates via Web UI and asynchronously via B2B message allows suppliers, typically of agricultural goods, to communicate with their customers the exact location that their product was produced on. Communicating the exact location where goods were produced allows downstream supply chain partners (e.g. 3PLs, Wholesalers) to verify the origin of the goods they receive, ensuring compliance with government regulations, such as the European Union Deforestation-free Regulation (EUDR) Information System (IS), that prohibit the sale of product sourced from illegal areas (e.g. land protected by deforestation laws).
In the Web UI, Owners can create geocoordinates; save a draft for submission at a later date; add, view, or delete individual geocoordinates to the transaction before submitting the geocoordinates to customers. Additionally, Owners can search for; view the details of the geocoordinates; and troubleshoot and resubmit geocoordinates.
For companies whose Partners do not own Multienterprise Information Network Tower, Owners can add their Partner's users to their network and assign them the appropriate roles to enable them to search for and view the details of geocoordinates in the Web UI using the Owner's instance of Multienterprise Information Network Tower.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot geolocation messages; leverage a record of their geocoordinate details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given geocoordinate message using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new JSON messages are available for sending or receiving geocoordinates in this release:
B2B_GeoLocation_IB_V3 (inbound) B2B_GeoLocation_OB_V3 (outbound) Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners Send and Receive Inventory Updates in IDoc and X12 Formats Companies that own or link to Multienterprise Process Link can exchange inventory updates with their Partners via TraceLink in IDoc and X12 formats. Exchanging inventory updates asynchronously via Multienterprise Process Link allows suppliers to communicate with their remote or third-party warehouses, 3PLs, or CMOs about changes to the available inventory for specific products. Communicating inventory updates allows companies to maintain accurate inventory records, which ensures compliance with government regulations, optimizes warehouse operations, reduces inefficiencies, and prevents stockouts or overstocks. Companies are also able to make informed decisions regarding procurement, production, and inventory management strategies.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot inventory update messages; leverage a record of their inventory update details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given inventory update using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving inventory updates in this release:
IDoc (inbound):B2B_IDoc_MBGMCR_MBGMCR03_InventoryUpdate_IB_V1 X12 (outbound):B2B_EDI_X12_947_InventoryUpdate_OB_V1 Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners Send and Receive Return Authorization Requests in X12 and IDoc Formats Companies that own or link to Multienterprise Process Link can exchange return authorization requests with their Partners via TraceLink in X12 and IDoc formats. Return authorization requests are initiated by buyers to obtain approval from sellers for returning goods due to defects, incorrect shipments, or excess stock, ensuring that the return process adheres to the terms of the purchase order. Exchanging return authorization requests asynchronously via Multienterprise Process Link allows buyers to issue return authorization request messages to suppliers.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot return authorization request messages; leverage a record of their return authorization requests details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given return authorization 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 inventory updates in this release:
X12 (inbound):B2B_EDI_X12_180_ReturnAuthorizationRequest_IB_V1 IDoc (outbound):B2B_IDoc_ORDERS_ORDERS05_ReturnAuthorizationRequest_OB_V1 Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners Send and Receive Return Authorization Responses in X12 and IDoc Formats Companies that own or link to Multienterprise Process Link can exchange return authorization responses with their Partners via TraceLink in IDoc and X12 formats. Return authorization responses communicate the approval or rejection status of a return authorization request to the buyer, along with return information, such as the return authorization number, return address, and shipping label. Exchanging return authorization responses asynchronously via Multienterprise Process Link allows suppliers to issue return authorization responses messages after processing return authorization requests from buyers.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot return authorization responses; leverage a record of their return authorization responses for business records or compliance purposes; and retrieve the input, output, and canonical files for a given inventory update using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving inventory updates in this release:
X12 (inbound):B2B_EDI_X12_180_ReturnAuthorizationResponse_IB_V1 IDoc (outbound):B2B_IDoc_ORDRSP_ORDERS05_ReturnAuthorizationResponse_OB_V1 Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners Enhancements to Existing Messages A number of existing transforms are updated to improve how TraceLink maps certain elements within the transform and elements and enumerations are added to the transforms to record additional information customers may want to include. The following existing message types have been updated and their transform versions incremented to the versions below:
Advanced Ship Notice transforms:B2B_IDoc_DELVRY07_ASN_IB_V2B2B_EDI_X12_856_AdvanceShipNotice_IB_V2B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_IB_V2 Batch transforms B2B_IDoc_BATMAS_BATMAS03_BatchMaster_IB_V2 Forecast transforms:B2B_IDoc_DELFOR_DELFOR02_ForecastPlanResponse_IB_V2B2B_IDoc_DELFOR_DELFOR02_ForecastPlan_OB_V2 Inventory Balance & Inventory Update transforms:B2B_IDoc_INVRPT_INVRPT01_InventoryBalance_IB_V2B2B_EDI_X12_846_InventoryBalance_IB_V2B2B_EDI_X12_947_InventoryUpdate_IB_V2 Invoice transforms:B2B_IDoc_INVOIC02_Invoice_IB_V2 Price Sales Catalog transforms:B2B_IDoc_PRICAT_PRICAT03_PriceSalesCatalog_IB_V2 Purchase Order & Purchase Order Acknowledgment transformsB2B_IDoc_ORDERS05_PurchaseOrder_IB_V4B2B_EDI_X12_850_PurchaseOrder_IB_V3B2B_EDI_EDIFACT_ORDERS_PurchaseOrder_IB_V3B2B_IDoc_ORDERS05_PurchaseOrderAcknowledgment_IB_V3B2B_EDI_X12_855_PurchaseOrderAcknowledgment_IB_V3B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_IB_V2 Remittance Advice transforms:B2B_IDoc_REMADV_PEXR2003_RemittanceAdvice_OB_V2B2B_EDI_X12_820_RemittanceAdvice_IB_V2 Warehouse Shipping Advice transformsB2B_IDoc_SHPCON_DELVRY07_ShipAdvice_IB_V2B2B_EDI_X12_945_WHS_ShipAdvice_IB_V3 Warehouse Shipping Order transformsB2B_IDoc_SHPORD_DELVRY03_ShipOrder_IB_V2B2B_EDI_X12_940_WHS_ShipOrder_IB_V2 Warehouse Stock Transfer Shipment Advice transformsB2B_IDoc_WMTORD_WMTOID02_WHS_StockTransferShipAdvice_IB_V2B2B_EDI_X12_943_WHS_StockTransferShipAdvice_IB_V2 Warehouse Stock Transfer Receipt AdviceB2B_IDoc_WMTOCO_WMTCID03_WHS_StockTransferReceiptAdvice_IB_V2B2B_EDI_X12_944_WHS_StockTransferReceiptAdvice_IB_V3 Additionally, the internal processing for the Serialized Shipment Notice message is updated, as a result, the transform version is updated to MPC\_STE\_EPCIS\_SerializedShipmentNotice\_1\_2\_IB\_V4. This update does not impact any customer facing elements in the transform.
Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners System features Multienterprise Process Link, version 2024.6.0M1 There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2024.6.0 There is no new or updated system functionality included in this release.
Resolved issues Multienterprise Process Link, version 2024.6.0M1 The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
Transform updates do not require any system changes and include content upgrades that do not impact other customer use of the system. The transforms are independently versioned and configured for use specifically by an Administrator at each company that will use them.
Partner transform updates are included to inform customers whose networks might include the particular Partner. Note that each transform update identifies the transform version number (e.g., \_V1\_1). Customers can request that their Partner upgrade to the noted transform version when necessary.
ID Interface Issue Description CMCP-37577: Update the Inbound IDoc Purchase Order Acknowledgment transform to Map Data from the SAPControlFileHeader. Web UI The field mapping for the control segment fields SNDPRN and RCVPRN were being incorrectly mapped from canonical fileSenderNumber and fileReceiverNumber by default. The field mapping for the control segment fields SNDPRN and RCVPRN are updated to map from the canonical IDoc control segment attributes fileSenderType/ediInterchangePartyValue and fileReceiverType/ediInterchangePartyValue, and only map canonical fileSenderNumber and fileReceiverNumber if the sapControlFileHeader values are not present.
Pre-Release Transform Name: B2B\_IDoc\_ORDERS05\_PurchaseOrderAcknowledgment\_OB\_V3
This issue has been resolved.
Multienterprise Process Link, version 2024.6.0 There are no resolved issues in this release.
Known issues Multienterprise Process Link, version 2024.6.0M1 There are no known issues in this release.
Multienterprise Process Link, version 2024.6.0 There are no known issues in this release.
[View More](/resources/tracelink-university/whats-new-multienterprise-process-link-version-20246)
[ ![Related content]() ](/resources/tracelink-university/whats-new-multienterprise-process-link-version-202510)
##### What's new in Multienterprise Process Link, version 2025.1.0
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
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).
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 patches are released for this version:
Multienterprise Process Link, version 2025.1.4M2 is available on Validation and Production on 13 May 2025. Multienterprise Process Link, version 2025.1.4M1 is available on Validation on 23 Apr 2025 and Production on 01 May 2025. Multienterprise Process Link, version 2025.1.4 is available on Validation on 17 Apr 2025 and Production on 01 May 2025. 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. 17 Apr 2025 08 The following updates have been made since the previous revision was distributed:Issue information for the Multienterprise Process Link, version 2025.1.4 patch is added: 1 issue is added to Resolved issues. 0 issues are added to Known issues. 23 Apr 2025 09 The following updates have been made since the previous revision was distributed:Issue information for the Multienterprise Process Link, version 2025.1.4M1 patch is added: 1 issue is added to Resolved issues. 0 issues are added to Known issues. 30 Apr 2025 10 The following update has been made since the previous revision was distributed:
The Production date for version 2025.1.4M1 patch in Patch releases is updated to 01 May 2025. 13 May 2025 11 The following updates have been made since the previous revision was distributed:Issue information for the Multienterprise Process Link, version 2025.1.4M2 patch is added: 11 issues are added to Resolved issues. 0 issues are added to Known issues. API features Multienterprise Process Link, version 2025.1.4M2 There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2025.1.4M1 There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2025.1.4 There is no new or updated API functionality included in this release.
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_V1B2B\_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_V1B2B_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.
Impact analysis
Interface options:API Business segment impacts:All business segments for both Owners and Partners System features Multienterprise Process Link, version 2025.1.4M2 There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2025.1.4M1 There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2025.1.4 There is no new or updated system functionality included in this release.
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_V2B2B_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.4M2 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-38756: PO ACK X12 IB Map Unrecognized Identifier Type: COMPANYID API The Purchase Order Acknowledgment X12 map was recognizing the type "COMPANYID" as " CUSTOM".
The transform has been updated to use lookup tables for mapping ISA05/ISA07, ensuring that "ZZ" attribute now correctly maps to "COMPANYID" instead of "CUSTOM".
Pre-Release Transform Name: B2B\_EDI\_X12\_855\_PurchaseOrderAcknowledgment\_IB\_V6.
This issue has been resolved.
CMCP-38764: Incorrect Value Mapped to ScheduleLineDates/dateType in Forecast Plan Response API The Forecast Plan Response IDoc transform was incorrectly mapping the value of "scheduleLineDates/dateType".
The transform has been updated to correctly map the "dateType" as "SCHEDULELINE" instead of "DELIVERYSCHEDULE" when extracting date information from the E1EDP16 segment in the source IDoc.
Pre-Release Transform Name: B2B\_IDoc\_DELFOR\_DELFOR02\_ForecastPlanResponse\_IB\_V3.
This issue has been resolved.
CMCP-38768: Incorrect Value Mapped to unitOfMeasure in Inventory Update API In the outbound WMMBID01 IDoc, the value "PK" was incorrectly mapped to the unitOfMeasure field as PK.
The transform has been updated to correctly map "PK" to "PAK" in the unitOfMeasure field.
Pre-Release Transform Name: B2B\_IDoc\_WMMBID\_WMMBID01\_InventoryUpdate\_OB\_V2.
This issue has been resolved.
CMCP-38908: Purchase Order EDIFACT Outbound Mapping Failed Due to Error API The Purchase Order EDIFACT outbound map was encountering errors, causing processing failures.
The following enhancements are made in the transform:
Eliminated errors related to incomplete address data in the NAD segment. Corrected the logic for mapping the purchase order date to use DTM01.1 = 4 instead of 137. Enhanced the transform to handle unsupported date types without throwing errors. Added support to QTY01.1 = 129 (PRICINGUNIT) and 187 (QUANTITYSCHEDULED). Enhanced the mapping to include product name or description in IMD03.4. Pre-Release Transform Name: B2B\_EDI\_EDIFACT\_ORDERS\_PurchaseOrder\_OB\_V4.
This issue has been resolved.
CMCP-38954: Forecast Plan X12 Outbound Mapping Error API The outbound B2B Forecast Plan X12 was failing due to missing required date values.
The following updates are made in the inbound transform:
Ensure that "mpcDates/dateValue" is correctly mapped when a "dateType" is specified, as required by the outbound map. Include document date in the logic to check for DTM02 when DTM01 = 166; if not present, it falls back to BPR08, and if BPR08 is also missing, it defaults to the required BPR06 element. Pre-Release Transform Name: B2B\_EDI\_X12\_830\_ForecastPlan\_IB\_V4.
This issue has been resolved.
CMCP-38955: Inbound PO ACK EDIFACT File Processing Issue API The inbound Purchase Order Acknowledgment EDIFACT map has been updated to correctly map values to the UNB02.2 and UNB02.3 segments.
Pre-Release Transform Name: B2B\_EDI\_EDIFACT\_ORDRSP\_PurchaseOrderAcknowledgment\_IB\_V3.
This issue has been resolved.
CMCP-38960: Inbound IDoc ASN Transform Failure Due to Error API The Inbound IDoc ASN transform was failing due to an error triggered when the Purchase Order Number was missing in the element "DELVRY07/IDOC/E1EDL20/E1EDL24/E1EDL41/BSTNR".
The transform has been updated to prevent the error from occurring when the field is not present.
Pre-Release Transform Name: B2B\_IDoc\_DELVRY07\_ASN\_IB\_V5.
This issue has been resolved.
CMCP-38962: ASN EDIFACT Outbound File Failure API The Advanced Shipping Notice EDIFACT outbound file was encountering failures during transformation in the outbound flow.
The following updates have been made to enhance the transformation logic:
Added support to date format code 203 to handle timestamps in the CCYYMMDDHHMM format. Enhanced Purchase Order mapping to populate RFF01.2 when RFF01.1 = "ON". Supported and mapped SUPPLIER identifier to "VN", in addition to the existing support for VENDOR. Updated the transform to no longer require a Purchase Order Number in files that do not include packing aggregation. Pre-Release Transform Name: B2B\_EDI\_EDIFACT\_DESADV\_AdvanceShipNotice\_OB\_V3.
This issue has been resolved.
CMCP-38964: ASN EDIFACT Inbound File Failure API The Advanced Shipping Notice EDIFACT document could not be parsed from the incoming file.
The transform has been updated to include mappings for "fileSenderType/ediInterchangePartyValue" attribute and "fileReceiverType/ediInterchangePartyValue" attribute to support proper file identification.
This issue has been resolved.
TL-68260: Inventory Balance Processing Failure Due to Error API The transform was updated to prevent errors when "mpcDates/dateType = EFFECTIVE" field is missing from the source, as this field is not mandatory.
Pre-Release Transform Name: B2B\_IDoc\_INVRPT\_INVRPT01\_InventoryBalance\_OB\_V2.
This issue has been resolved.
TL-68929: Incorrect Mapping of Date Format Code in ASN EDIFACT Outbound File API The target field DTM01.3 (date format code) in the ASN outbound EDIFACT transform was displaying 304 code instead of the expected 102 code.
The transform has been enhanced to include support for additional date format codes in the target field DTM01.3, specifically adding DTM01.3 = 203 for the YYYYMMDDHHMM format and DTM01.3 = 304 for the CCYYMMDDhhmm format.
Pre-Release Transform Name: B2B\_EDI\_EDIFACT\_DESADV\_AdvanceShipNotice\_OB\_V3.
This issue has been resolved.
Multienterprise Process Link, version 2025.1.4M1 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-38916: System Unable to Generate Draft Forecast Plan Response API The Forecast Plan Copy Into feature failed to create a draft Forecast Plan Response due to a missing default value for the Forecast Period in the TraceLink system.
This issue has been resolved.
Multienterprise Process Link, version 2025.1.4 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 TL-68616: Updated Canonical Schema Data Models API Some attributes and enumeration values were missing. The following canonical schema data models have been updated to improve transaction usability:
Created new objects and attributes, including updates to canonicalPurchaseOrder and canonicalPurchaseOrderHeaderTypeDefinition, additions to mpcPartnerTypeDefinition for mapping to NAME2, creation of processOrderComponentList with the billOfMaterialsComponentsTypeDefinition array and processOrderData with processOrderDataTypeDefinition, updates to existing type definitions with new attributes and object types in the Purchase Order transaction. Updated canonicalPurchaseOrderHeaderTypeDefinition, mpcPartnerTypeDefinition, and canonicalPurchaseOrderItemDetails, including modifications to the existing processingFunctionTypeCode attribute and the addition of new enumeration values across attributes in the Purchase Order Acknowledgment transaction. New attributes—customerLotNumber, freeTextNote (as an array), and customFields using the nameValueTypeDefinitionTypeDefinition array—were added to the canonical schema for the Inventory Balance transaction.
Attribute mappings were added to resolve discrepancies between the inbound and outbound canonical versions of the Advance Shipment Notices. This issue has been resolved.
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 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.
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 EN 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.
Known issues Multienterprise Process Link, version 2025.1.4M2 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.4M1 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.4 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.3 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.2M1 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.2 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.1 There are no known issues in this release.
Multienterprise Process Link, version 2025.1.0 There are no known issues in this release.
[View More](/resources/tracelink-university/whats-new-multienterprise-process-link-version-202510)