Table of contents
To learn more about what's new in the Multienterprise Information Network Tower, solution version 14.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.2.0 app release, which is available on Validation on 12 Jun 2025 and Production on 26 Jun 2025.
The following apps are impacted by this release and will be updated to the version listed:
- Multienterprise Process Link, version 2025.2.0
Solutions supported by this app version:
- Multienterprise Information Network Tower, solution version 14.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 patch is released for this version:
- Multienterprise Process Link, version 2025.2.1 is available on Validation on 17 Jul 2025 and Production on 31 Jul 2025.
- Multienterprise Process Link, version 2025.2.0M1 is available on Validation and Production on 01 Jul 2025.
These patches are cumulative, and the most recent patch release includes functionality from all previous versions.
Revisions
| Date | Revision | Description |
|---|---|---|
| 05 Jun 2025 | 01 | Initial version. |
| 12 Jun 2025 | 02 | The following updates have been made since the previous revision was distributed:
|
| 01 Jul 2025 | 03 | The following updates have been made since the previous revision was distributed:
|
| 17 Jul 2025 | 04 | The following updates have been made since the previous revision was distributed:
|
API features
Multienterprise Process Link, version 2025.2.1
There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2025.2.0M1
There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2025.2.0
The following new or updated API functionality is included in this release.
Send and Receive Article Masters in IDoc Format
Companies that own or link to Multienterprise Process Link can exchange article masters with their Partners via TraceLink in IDoc format. The article master allows the MAH to align with 3PLs by sharing product details needed for inventory management and handling requirements. Exchanging article masters asynchronously via Multienterprise Process Link maintains consistency, enabling traceability, and supporting operational efficiency across manufacturing, warehousing, distribution, and retail processes.
Additionally, sending and receiving article masters asynchronously via Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot article masters status messages; leverage a record of their article master details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given article master using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving article masters in this release:
- IDoc (inbound and outbound):
B2B_IDoc_MATMAS_MATMAS05_ArticleMaster_IB_V1
B2B_IDoc_MATMAS_MATMAS05_ArticleMaster_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Order Status Reports in IDoc and X12 Formats
Companies that own or link to Multienterprise Process Link can exchange order status reports with their Partners via TraceLink in IDoc and X12 formats. A order status report provides a structured way for suppliers or CMOs to share real-time updates on the status of open purchase orders with their customers or MAHs. Exchanging order status reports asynchronously via Multienterprise Process Link allows downstream partners to stay informed throughout the order lifecycle by receiving regular updates that help manage expectations, reduce uncertainty, and improve planning and collaboration.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot order status report messages; leverage a record of their order status report for business records or compliance purposes; and retrieve the input, output, and canonical files for a given order status report using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving order status reports in this release:
- IDoc (inbound):
- SAP_IDoc_ORDRSP_ORDERS05_OrderStatusReport_IB_V1
- X12 (outbound):
- B2B_EDI_X12_870_OrderStatusReport_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Price Authorization Acknowledgments in X12 Format
Companies that own or link to Multienterprise Process Link can exchange price authorization acknowledgments with their Partners via TraceLink in X12 format. The price authorization acknowledgment ensures both the buyer and seller are aligned on product pricing, contract terms, and eligibility before transactions occur. Exchanging price authorization acknowledgments asynchronously via Multienterprise Process Link ensures both parties agree on the effective pricing before orders, chargebacks, or rebates are processed, enhancing decision-making speed, data accuracy, and reliability by minimizing manual entry errors.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot price authorization acknowledgment messages; leverage a record of their price authorization acknowledgment for business records or compliance purposes; and retrieve the input, output, and canonical files for a given price authorization acknowledgment using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving price authorization acknowledgments in this release:
- X12 (inbound and outbound):
B2B_EDI_X12_845_PriceAuthorizationAcknowledgment_IB_V1
B2B_EDI_X12_845_PriceAuthorizationAcknowledgment_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Planned Orders in IDoc Format
Companies that own or link to Multienterprise Process Link can exchange planned orders with their Partners via TraceLink in IDoc format. MAHs can send planned orders to CMOs, who in turn create process orders in their ERP system to plan production. These planned orders are generated during Material Requirements Planning (MRP) runs in the MAH's ERP system. Exchanging planned orders asynchronously via Multienterprise Process Link indicates when and how much of a material should be ordered to meet expected demand and can be created either manually by planners or automatically during MRP runs.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot planned order messages; leverage a record of their planned order details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given planned order using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving planned orders in this release:
- IDoc (inbound and outbound):
SAP_IDoc_LOIPLO-LOIPLO02_PlannedOrder_IB_V1
SAP_IDoc_LOIPLO-LOIPLO02_PlannedOrder_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Process Orders in IDoc Format
Companies that own or link to Multienterprise Process Link can exchange process orders with their Partners via TraceLink in IDoc format. Process order allows MAH sends a Planned Order to a CMO, who creates a process order in their ERP system to plan production to plan and manage manufacturing activities. After the planned order is received the CMO sends a Process Order Release transaction to the MAH, providing visibility into production and enabling downstream coordination. Exchanging process orders asynchronously via Multienterprise Process Link manages production processes that involve changing materials and supports accurate control of continuous or semi-continuous manufacturing.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot process orders messages; leverage a record of their process order details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given process order using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving process orders in this release:
- IDoc (inbound and outbound):
SAP_IDoc_LOIPRO_LOIPRO04_ProcessOrder_IB_V1
SAP_IDoc_LOIPRO_LOIPRO04_ProcessOrder_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Product Transfer Account Adjustment Requests in X12 Format
Companies that own or link to Multienterprise Process Link can exchange product transfer account adjustment requests with their Partners via TraceLink in X12 format. The product transfer account adjustment request allows the buyer to communicate with the supplier ensure the accuracy of financial records and reconcile discrepancies between invoices, payments, and outstanding balances. Product Transfer Account Adjustment transactions are used to correct errors or make adjustments to previously recorded financial transactions. In both cases, adjustments are made to the accounts receivable ledger to reflect the corrected balances. Exchanging product transfer account adjustment requests asynchronously via Multienterprise Process Link involves adjustments made to accounts related to product transfers, which may include chargebacks, returns, credits, or any other financial transactions associated with the movement of products between trading partners.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot product transfer account adjustment request messages; leverage a record of their product transfer account adjustment request for business records or compliance purposes; and retrieve the input, output, and canonical files for a given product transfer account adjustment 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 product transfer account adjustment requests in this release:
- X12 (inbound and outbound):
B2B_EDI_X12_844_ProductTransferAccountAdjustmentRequest_IB_V1
B2B_EDI_X12_844_ProductTransferAccountAdjustmentRequest_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Product Transfer Account Adjustment Responses in X12 Format
Companies that own or link to Multienterprise Process Link can exchange product transfer account adjustment responses with their Partners via TraceLink in X12 format.The product transfer account adjustment responses allows the suppliers or the MAHs to communicate the outcome of the product transfer account adjustment request with the buyer or the distributor. It informs any approved adjustments, partial denials, or explanations; and the final credit amounts to be applied to the account. Exchanging product transfer account adjustment responses asynchronously via Multienterprise Process Link create a closed-loop communication for automated rebate and chargeback processing in B2B commerce.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot product transfer account adjustment responses messages; leverage a record of their product transfer account adjustment responses for business records or compliance purposes; and retrieve the input, output, and canonical files for a given product transfer account adjustment responses using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving product transfer account adjustment responses in this release:
- X12 (inbound and outbound):
B2B_EDI_X12_849_ProductTransferAccountAdjustmentResponse_IB_V1
B2B_EDI_X12_849_ProductTransferAccountAdjustmentResponse_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Product Transfer Resale Reports in X12 Format
Companies that own or link to Multienterprise Process Link can exchange product transfer resale reports with their Partners via TraceLink in X12 format. The product transfer resale report allows wholesaler or distributor to communicate with manufacturer insights into product movements such as sales, location changes, and returns, helping the vendor assess product performance across various locations and end consumers. Exchanging product transfer resale reports asynchronously via Multienterprise Process Link provides information about transferred products, product sales to end customers, demand lost orders, and sales and returns linked to rebates.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot product transfer resale report messages; leverage a record of their product transfer resale report for business records or compliance purposes; and retrieve the input, output, and canonical files for a given product transfer resale report using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving product transfer resale reports in this release:
- X12 (inbound and outbound):
B2B_EDI_X12_867_ProductTransferResaleReport_IB_V1
B2B_EDI_X12_867_ProductTransferResaleReport_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Standard Reports in External Manufacturing Orchestration
Companies that own Multienterprise Process Link and their Partners can use standard reporting across all External Manufacturing orchestrations. This enhancement supports both existing and future transactions, ensuring each orchestration has baseline visibility and access to scalable, actionable analytics. As manufacturing operations become increasingly complex and data-driven, the need for consistent and reliable access to transaction-level insights becomes more important than ever.
Multienterprise Information Network Tower users do not have the ability to add reports to a Multienterprise Information Network Tower solution. Only the Opus Solution Environment (OSE) user who creates the Multienterprise Information Network Tower solution can select reports from the report catalog and add them to the solution. Once added, the reports appear in the left-hand navigation menu.
By default, Multienterprise Information Network Tower solutions are deployed with a predefined set of reports. If the company is licensed for Multienterprise Information Network Tower, users will see the standard reports in the menu.
If the company is licensed for both Multienterprise Information Network Tower and OSE, authorized OSE users can customize the solution by adding or removing reports from the configuration. Users with appropriate roles can view the reports linked to MINT solution.
In this release, the external manufacturing orchestration includes the following report types:
- Base Reports - Standard reports per transaction.
- Joint Reports - Combined reports across the orchestrations and within the orchestration.
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
System features
Multienterprise Process Link, version 2025.2.1
There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2025.2.0M1
There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2025.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.
MPL Exception Handling for Business Transactions and Serialization Transactions
The Multienterprise Process Link has been enhanced to more effectively handle errors related to Business Transactions (BTO) and Serialization Transactions (STO). This improvement ensures that previously silent failures are now captured and reported with clear error codes and messages, enabling faster issue identification and resolution.
The update includes changes to how errors are flagged internally, using improved functions to ensure that failures are handled accurately and transparently. The following is a summary of the key updates:
- Update Required: The error handling implementation is being improved by replacing outdated methods with updated functions to enhance accuracy and consistency in error reporting.
- Failure Scenarios: Errors may occur under various conditions, such as missing values or due to misconfiguration.
- Error Messages: Clear and specific error messages have been defined for each failure scenario to help users quickly understand the issue and take the appropriate steps.
- Corrective Actions: Users are advised to retry the transaction with correct information. If problems persist, they should contact support for further assistance.
Impact analysis
- Business segment impacts:
- All business segments for both Owners and Partners
Stabilization and Usability Enhancements
To support new requirements, previously released transaction canonicals were enhanced to include additional attributes and enumeration values as needed. Updates were also made to the underlying canonical schema data models, along with other improvements.
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.2.1
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-38762: Duplicates Created in ForeCast Plan Response | API | Multiple forecastPlan were created with "copyInto" object operation on the Opus Lab environment as the copyInto decider handler was not returning any response. The "copyInto" handler has been updated to return a proper response after execution, preventing unnecessary retries and duplicate object creation. This issue has been resolved. |
| CMCP-39138: Inventory Balance Processing Issue | API | MINT transactions sent from a Partner Location to the company were failing at the Prepare Inbound step. The transaction logic has been updated to require and process the fkPartnerNodeId field. This issue has been resolved. |
| CMCP-39267: Delays in DataMesh Message Consumption | API | A performance lag in Datamesh was causing delays in processing transactions for Compliance applications and MINT. Performance improvements are made to address the lag in Datamesh. This issue has been resolved. |
| CMCP-39325: Invoices Fail to Send Due to processStatus Handling Error | API | During recoverable intermittent internal server errors, MINT was not performing automatic retries as expected. This led to unnecessary transaction failures even though the errors were retryable. MINT has been enhanced with a new flag, isRetryableByDefault: true, which enables automatic retries for eligible recoverable errors. This issue has been resolved. |
| CMCP-39362: Missing PO OB Reference Identifier in Outbound Canonical | API | The outbound canonical for inbound purchase orders was missing the "mpcadditionalAddressinformation" field. As a result, the output file defaulted to 'new', potentially leading to incorrect address data and processing errors. The canonical mapping logic has been updated to ensure the "mpcadditionalAddressinformation" field is correctly populated in the outbound file. This fix improves data accuracy and alignment with expected purchase order formatting. This issue has been resolved. |
| CMCP-39432: Price Sales Catalog Line Items Not Fully Visible in MINT UI | API | A price sales catalog transaction was initiated via SFTP, containing multiple line items; however, only a single line item is visible in the MINT UI. The system maps are updated to correctly process and display all line items. The MINT UI now reflects the complete set of data. This issue has been resolved. |
| CMCP-39451: Missing Value in the WSA Subtype Attribute | API | A WSA subtype attribute had an incomplete picklist that was missing one expected value, even though the value was allowed in the canonical model. This caused affected transactions to fail during processing. The missing value is added to the picklist. This issue has been resolved. |
| CMCP-39476: Missing Purchase Order Values in MINT UI | API | The JavaScript map used by MINT to convert canonical Purchase Order data to UI attributes contained an error, preventing values from displaying correctly in the UI. The mapping logic is corrected. Purchase Order data now displays as expected in the MINT UI. This issue has been resolved. |
| CMCP-39478: Missing Report Date Causes Inventory Balance Failure | API | Inventory balance transactions were failing with the error “Date of inventory balance report is required.” This occurred due to an error in the system mapping logic, which failed to populate the required date field. The system map has been corrected to ensure the report date is properly mapped. This issue has been resolved. |
| CMCP-39526: Inbound Failure for PO Acknowledgment Submitted via UI | API | PO acknowledgment transactions submitted through the UI were failing during inbound processing due to a system transformation error. The issue is resolved by correcting the system transform logic. This issue has been resolved. |
| CMCP-39565: Error in Account Adjustment Response for Product Transfer | API | The transaction was failing because certain attributes in the Product Transfer Account Adjustment Response were not being populated due to an issue with the copyInto object operation. The system map has been updated to resolve the issue. The affected attributes are now correctly populated, and transactions are processing successfully. This issue has been resolved. |
| CMCP-39591: Enhanced Web UI Support for Product Activity Subtypes | API | The "quantityActivityCode" attribute was missing expected enumertaion values, resulting in incomplete data representation. The "commerceSentProductActivity" and "commerceReceivedProductActivity" subtypes are enhanced to improve the user experience at the line-item level. These updates provide better clarity and usability across related product activity transactions. This issue has been resolved. |
| CMCP-39604: Incorrect Mapping of Quantity Type in WSTSA Transactions | API | In WSTSA transactions, the quantityValue with type DELIVERY in the inbound canonical was incorrectly mapped as type ITEM in the outbound canonical. The specification and system mapping are updated to preserve the correct quantity type. This issue has been resolved. |
| CMCP-39605: Missing Mappings in OB Canonical | API | In WSTSA transactions, the supplierBusinessInformation present in the inbound (IB) canonical was not appearing in the outbound (OB) canonical due to missing mapping logic. The specification and system maps are updated to ensure proper data flow between the inbound and outbound canonical structures. This issue has been resolved. |
| CMCP-39634: Missing Rush Order Enumeration in Purchase Order Type Picklist | API | The "Rush Order" enumeration value was missing from the "purchaseOrderType" picklist attribute across all Purchase Order subtypes, limiting available PO type selections. The "Rush Order" enum has been added for all Purchase Order subtypes to ensure complete type coverage. This issue has been resolved. |
| TL-74483: Autofill Not Working in Product Transfer Resale UI | API | In the Customer Product Transfer Resale Report transaction, panels were not loading and address fields were not autofilling as expected. Autofill is now functioning correctly for Customer (as partner) in Customer Product Transfer Resale transactions. Additionally, Line Item Reference Address panels are now visible in the UI. |
| TL-74605: Article Master Transaction Fails on UI Submission Due to Decimal Configuration | API | Article Master transactions are failing when created from the UI. The issue is traced to the isThresholdPicking field in the Article Master transaction subtype, which is an RFT percentage attribute. |
| TL-75078: PO ACK Failure Due to Missing acknowledgmentType Value | API | PO acknowledgment (PO ACK) transactions were failing for Ropack in a specific use case where the acknowledgmentType value was set to ACCEPTEDWITHCHANGES. This value was not present in the allowed picklist for the PO ACK subtype. The PO ACK subtype data model is updated to include and support the ACCEPTEDWITHCHANGES value in the acknowledgmentType picklist.
This issue has been resolved. |
| TL-75312: Missing Attributes in Article Master Canonical | API | Article Master was missing some attributes and enum values. The following two new attributes have been added to the Article Master canonical object to improve data completeness and support more accurate product representation.
Pre-Release Transform Name: B2B_IDoc_MATMAS_MATMAS05_ArticleMaster_OB_V2 This issue has been resolved. |
Multienterprise Process Link, version 2025.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-39098: Outbound ASN IDoc Failure | API | The outbound ASN IDoc failed due to a restricted values list on "processingFunctionTypeCode". This restriction is removed and the mapping logic in the E1EDK18 segment is updated to accept both CREATE and ORIGINAL values. Pre-Release Transform Name: B2B_IDoc_DELVRY07_ASN_OB_V4. This issue has been resolved. |
| CMCP-39200: Missing N1BS, N1OB, and Product Code Callout Table in Standard Purchase Order Inbound Map | API | The standard Purchase Order inbound map was missing "N1*BS" for "billtoShipToInformation", "N1*OB" for "orderedByInformation" attributes. The map is updated to include these missing attributes and support for the product code callout table. Pre-Release Transform Name: B2B_EDI_X12_850_PurchaseOrder_IB_V7. This issue has been resolved. |
| CMCP-39235: Missing Mappings in Outbound PO Acknowledgment and ASN | API | Some attributes and enumeration values were missing in the Outbound PO Acknowledgment and ASN transform maps. The following transforms are updated to meet the requirements:
Pre-Release PO Ack Transform Name: B2B_EDI_EDIFACT_ORDRSP_PurchaseOrderAcknowledgment_IB_V4 Pre-Release ASN Transform Name: B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_IB_V5 This issue has been resolved. |
| CMCP-39288: Implemented EDI X12 852 Outbound Transformation for Product Activity Transactions | API | To enable communication of inventory activity between trading partners such as inventory levels, product movement, and sales data from a retailer to a supplier, the existing Product Activity transaction is mapped to the EDI X12 852 format in compliance with ANSI X12 standards. Pre-Release Transform Name: B2B_EDI_X12_852_ProductActivity_OB_V1. This issue has been resolved. |
| CMCP-39295: Enhanced Error Handling for Inbound EDI 852 Transformation | API | The Product Activity transform (EDI 852) is updated to support LIN product code ND and quantity unit of measure CS. The enhancement also includes support for the MP segment and improved error handling in the CTT segment. Pre-Release Transform Name: B2B_EDI_X12_852_ProductActivity_IB_V2. This issue has been resolved. |
| CMCP-39299: Missing Mappings in Inbound Warehouse Ship Order and Warehouse Ship Advice Transactions | API | Some attributes and enumeration values were missing n Inbound Warehouse Ship Order and Warehouse Ship Advice transforms. The following transforms are updated to meet the requirements:
Pre-Release WSO Transform Name: B2B_EDI_X12_940_WHS_ShipOrder_IB_V3 Pre-Release WSA Transform Name: B2B_EDI_X12_945_WHS_ShipAdvice_IB_V4 This issue has been resolved. |
| CMCP-39490: Misalignment in Standard X12 PO Inbound and Outbound Maps | API | The "Supplier Street" field was misaligned between the Standard X12 Purchase Order inbound and outbound maps. This update resolves the discrepancy and adds support for "ITD01=09 (PROXIMO)", "N1*BS (BillToAndShipTo)", "N1*OB (OrderedBy)", and "PO106=UI (PackageUPC)". Pre-Release Transform Name: B2B_EDI_X12_850_PurchaseOrder_OB_V7 This issue has been resolved. |
| CMCP-39523: Improved Support for Identifiers and Segments in Price Sales Catalog Map | API | The transform was updated to address gaps identified during data analysis. Enhancements include improved support for multiple identifiers, date types, and business information, along with additional segment support for TXI, SLN, and CTP. Key updates include new mappings for contract effective and expiration dates, seller and system business details, product codes, and transaction references. Pre-Release Transform Name: B2B_EDI_X12_832_PriceSalesCatalog_OB_V2. This issue has been resolved. |
| TL-72408: Enhanced Map Logic for Optional Purchase Order Based on Aggregation | API | The B2B_EDI_X12_856_AdvanceShipNotice_OB_V3 outbound and B2B_EDI_X12_856_AdvanceShipNotice_IB_V4 inbound transforms are updated to make the Purchase Order number optional when using the SOI hierarchy (no aggregation). Pre-Release Transform Name: B2B_EDI_X12_856_AdvanceShipNotice_IB_V5 and B2B_EDI_X12_856_AdvanceShipNotice_OB_V4 This issue has been resolved. |
Multienterprise Process Link, version 2025.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-38140: STE Transaction Not Visible in MINT UI | API | Although shipments were successfully sent to partners, they were missing in Opus because of intermittent timeout errors while accessing the inbound STE transactions from CTA. This issue has been resolved. |
| CMCP-38795: Mapping Error in Preparing to Send Step of Forecast Plan | API | Creation of Forecast Plan failed during the "Preparing to Send" step due to a mapping error. This issue has been resolved. |
| TL-51948: Incorrect String Type for QuantityValue in New ASN Pages | API | The "QuantityValue" field in "btoAsnItemDetails" has been updated from a string to a number format in the Sent and Received ASN New Pages. This ensures correct data handling and consistency across integrations. This issue has been resolved. |
| TL-59744: Intermittent S3 Failures Caused by Expired Presigned URLs | API | Users encountered failures when presigned URLs expired due to processing delays over 60 seconds, often due to intermittent slowness, causing the presigned URL to expire before the transaction could complete. Enhanced handling has been added to automatically retry the step and renew the URL timeout, ensuring smooth transaction completion. This issue has been resolved. |
| TL-70460: Missing Mapping ASN Line Item referenceTransactionIdentifierList to Base | API | The references provided in the header-level "referenceTransactionIdentifierList" were copied to the Base. References included at the line item level were not transferred. Now both header and line item references are correctly copied to the Base for accurate downstream processing. This issue has been resolved. |
| TL-70593: Canonical Schema Data Model Enhancements | API | The transaction canonicals were enhanced to include additional attributes and enumeration values where needed. The following transaction canonicals were updated:
This issue has been resolved. |
| TL-71449: : Failure in Forecast Plan Draft to Submit State | API | Exception handling is added to display an error message on the B2B Transaction screen when a failure occurs in the Draft to Submit state. This enhancement helps users quickly identify and address submission issues. This issue has been resolved. |
| TL-71586: Missing Mapping from Subtype Header and Line Items to Base | API | References provided in both the subtype header and line item levels of the "referenceTransactionIdentifierList" were not being copied to the Base "referenceTransactionIdentifierList". This issue has been resolved. |
Known issues
Multienterprise Process Link, version 2025.2.1
There are no known issues in this release.
Multienterprise Process Link, version 2025.2.0M1
There are no known issues in this release.
Multienterprise Process Link, version 2025.2.0
The following known issues are included in this release and will be fixed in a future patch release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| TL-74483: Panels and Address Autofill Not Loading in Customer Product Transfer Resale Report | API | In the Customer Product Transfer Resale Report transaction, panels are not loading and address fields are not autofilling as expected. |
| TL-74605: Validation Error on isThresholdPicking Attribute in Article Masters | API | The "isThresholdPicking" field in the Article Masters transaction only accepts whole-number percentages, causing validation errors when decimal values (e.g. 0.5%) is used. |
