Tracelink University

What's new in Multienterprise Information Network Tower, solution version 19.0.0

Explore what's new in the Multienterprise Information Network Tower, solution version 19.0.0 release. What's new in the user interface.

Release information

This document describes the TraceLink capabilities included in the Multienterprise Information Network Tower, solution version 19.0.0 release, which is available on Validation on 03 Sep 2026 and Production on 20 Sep 2026.

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

Multienterprise Information Network Tower, solution version 19.0.0
Apps that support this solution version:
- Multienterprise Process Link, version 2026.3.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.

Revisions

Date	Revision	Description
20 Aug 2026	01	Initial version.
03 Sep 2026	02	The following updates have been made since the previous revision was distributed: The Production release date is updated from 04 Oct 2026 to 20 Sep 2026 in Release information section. The Expanded Logistics Orchestration Support for 4PL Operations feature is added. 7 issues are added to Resolved issues. 0 issues are added to Known issues.

Features

Multienterprise Information Network Tower, solution version 19.0.0

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

Send and Receive Customs Status Information in the Web UI

Companies that own Multienterprise Information Network Tower can send and receive Customs Status Information in the Web UI. Customs Status Information allows customs authorities to electronically communicate shipment status updates to authorized trading partners throughout the customs clearance process. Updates can include cargo release, cargo hold, and clearance progress. Authorized trading partners can include importers, exporters, customs brokers, customs agents, terminal operators, carriers, and service providers.

In the Web UI, Owners and Partners can:

Create new Customs Status Information
Save drafts for later submission
Edit line items including ports and conveyance details, and conveyance equipment details
Search for and view Customs Status Information details
Troubleshoot and resubmit Customs Status Information as needed

If a Partner does not own Multienterprise Information Network Tower, the Owner can add the Partner users to the Owner's network and assign the appropriate roles. Partner users can then create, draft, submit, search for, and view Customs Status Information in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Customs Status Information are now available in the transportation orchestration.

Impact analysis

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

Send and Receive Customs Events Advisory Details in the Web UI

Companies that own Multienterprise Information Network Tower can send and receive Customs Events Advisory Details in the Web UI. Customs Events Advisory enables transportation organizations to electronically communicate significant cargo events to customs authorities and government agencies during international trade. Transportation organizations can include carriers, freight forwarders, and logistics providers. Cargo events can include arrivals, departures, transfers, in-bond movements, and other status updates.

In the Web UI, Owners and Partners can:

Create and submit Customs Events Advisory Details
Save drafts for later submission
Edit line items, including Custom Ports Or Terminal Information, cargo manifest and equipment information, and shipment measurements
Search for and view Customs Events Advisory Details details
Troubleshoot and resubmit Customs Events Advisory Details if needed

If a Partner does not own Multienterprise Information Network Tower, the Owner can add the Partner users to the Owner's network and assign the appropriate roles. Partner users can then create, draft, submit, search for, and view Customs Events Advisory Details in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Customs Events Advisory Details are now available in the transportation orchestration.

Impact analysis

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

Send and Receive Motor Carrier Bills of Lading in the Web UI

Companies that own Multienterprise Information Network Tower and their Partners can send and receive Motor Carrier Bills of Lading in the Web UI. Motor Carrier Bills of Lading enables shippers, brokers, and third-party logistics (3PL) providers to electronically communicate Bills of Lading information and transportation instructions to motor carriers before shipment pickup. Information can include shipment details, origin and destination information, freight descriptions, and special handling requirements.

In the Web UI, Owners and Partners can:

Create and submit Motor Carrier Bills of Lading
Save drafts for later submission
Edit line items, including equipment and container information, carrier sequence information, dangerous goods contact and reference details, and consignment commodity details
Search for and view Motor Carrier Bills of Lading details
Troubleshoot and resubmit Motor Carrier Bills of Lading if needed

If a Partner does not own Multienterprise Information Network Tower, the Owner can add the Partner users to the Owner's network and assign the appropriate roles. Partner users can then search for and view Motor Carrier Bills of Lading in the Web UI using the Owner's instance of Multienterprise Information Network Tower.

The Motor Carrier Bills of Lading are now available in the transportation orchestration.

Impact analysis

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

Create New Discussion and Add Comment to Existing Discussion from Transaction View Page

This release adds contextual collaboration to subtype view pages, enabling faster and more transparent collaboration between owner and partner companies by keeping conversations connected to the relevant transaction. Owner and partner users can now start a new discussion or add a comment to an existing discussion directly from the business object they are viewing.

Users can now:

Select Add Discussion from a subtype view page to create a new discussion associated with that subtype or transaction.
Select Add Comment from a subtype view page to find an existing discussion related to the transaction and add a new comment.
Collaborate with users across owner and partner companies in the context of the relevant business object.
Keep discussion activity tied to the appropriate subtype or transaction for improved visibility and traceability.

When a user starts a new discussion, the system opens a new discussion page in a separate browser tab and automatically references the transaction from the originating subtype view page. When adding a comment, the system opens a discussion search page in the context of the selected transaction, allowing the user to choose the relevant existing discussion before commenting.

Impact analysis

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

Added Multi-Field Search Filter on all Transaction Search pages

Transaction Search pages now include a Multi-Field Search filter by default. The filter allows users to search multiple indexed text fields with a single keyword instead of selecting individual fields.

When a keyword is entered, MINT searches the indexed text fields for the corresponding business object. Search results can include matches from transaction identifiers, descriptions, statuses, Partner names, and other indexed transaction data.

The Multi-Field Search filter is available by default in the Filter Panel on all Transaction Search pages and cannot be removed by page authors.

Key Benefits:

Search transaction records across multiple fields with a single keyword.
Find information without knowing which field contains the value.
Provide a consistent search experience across Transaction Search pages.
Ensure the search filter is always available in the Filter Panel.

Impact analysis

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

Transaction Failed in ERP Due to Data Mismatch or configuration issues

The Redeliver Failed Transaction capability allows authorized MINT Owner users to redeliver failed outbound B2B transactions. Users must be assigned the MINT – Super Admin role to use this capability. An outbound B2B transaction can fail because of an ERP data mismatch or configuration issue. After the issue is corrected, the user can redeliver the same transaction directly from MINT. The trading partner does not need to resend the transaction.

Key Points

Redelivers the same failed outbound B2B transaction directly from MINT.
Reduces dependency on trading partners to resend failed transactions.
Shortens transaction recovery time and improves operational efficiency.
Gives MINT Owners greater control over failed transaction processing.
The Redeliver action is available from the following pages:
- Business Transaction view page
- Serialization Traceability view page

Impact analysis

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

Expanded Logistics Orchestration Support for 4PL Operations

Logistics Orchestration now supports Fourth-Party Logistics (4PL) operating models for Purchase Orders (PO) and Advance Shipment Notices (ASN) transactions. This enhancement enables 4PL providers to send operational and shipment information directly to their clients, providing centralized visibility across the shipment lifecycle.

Unlike the 3PL Commerce Orchestration model, where the client sends transaction and fulfillment information to the logistics provider for execution, the 4PL model supports the reverse flow. The logistics provider sends relevant PO and ASN information to the client, helping them monitor activities managed on their behalf across 3PLs, carriers, freight forwarders, warehouses, customs brokers, and other logistics partners.

Impact analysis

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

Standard PickLists for MPL and Canonical Object Fields

MINT now provides standard PickLists for selected fields in Master Product List subtypes and Canonical Objects. These PickLists offer a consistent set of values for applicable fields, replacing manually defined values with standardized options. This enhancement improves data consistency, reduces the risk of manual entry errors, and supports more reliable processing and integrations across MINT.

Impact analysis

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

Standard Reports in Transportation Orchestration

In this release new Transportation orchestration base reports are now available. These reports provide a standardized starting point for monitoring transportation workflows and reviewing transaction activity.

Users can use the reports to gain greater visibility into transportation-related operational data. They can review relevant transaction details and analyze orchestration activity. Users can also filter, group, and select data based on their operational needs.

Impact analysis

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

Stabilization and Usability Enhancements

MINT now provides more control and visibility for inbound shipment processing. Shipment events from Serialized Operations Manager and STE are processed only when enabled for a Process Network, which helps prevent unintended processing. Existing configured customers are migrated automatically to preserve their current workflows.
MINT also sends automated notifications for shipment processing failures caused by B2B transformation errors or missing location identifiers for unlinked Partners. These notifications help administrators identify and troubleshoot shipment processing failures.
This release includes the following user interface improvements:
- The line item information reference transaction now displays the View Panel and shows the transaction type in the page header.
- The Product Activity Search page now supports saving filters that include the productActivityPurposeCode field without errors.
- The View Panel is now available for subline-item temperature and dangerous goods details in the Ocean Shipment Booking Request workflow.
- The View Panel access button is restored on the Supplier_extManufacturingSentRemittanceAdvice page, enabling access to invoice and adjustment details.
- The Price Authorization Acknowledgment customer and supplier views now correctly display the New button, restore the edit and currency panels, and support creating related reference transactions.
- The View button is now available for nested line items in Third Party Logistics Sent Shipping Advice, providing access to detailed line item information.
- Shipment Dimensions are now available in the Stop Point and Shipment Details sections of Motor Carrier Load Tenders, making shipment size information easier to review.

Impact analysis

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

Resolved issues

Multienterprise Information Network Tower, solution version 19.0.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- 43026: Copy Into PO Ack Line Item Edits Were Not Retained	Web UI	When creating a Purchase Order Acknowledgement (PO Ack) from a Purchase Order using Copy Into, line item edits such as quantity or delivery date changes were not retained after the PO Ack was completed. To fix the issue, the PO Ack maps are updated to retain line item edits ensure that the updated values are reflected in the MINT UI and the generated output file. This issue has been resolved.
CMCP- 43094: ASN Reports Failed to Load in OPUS Reports and Dashboards	Web UI	OPUS Reports and Dashboards (ORD) reports for Advance Ship Notice (ASN) transactions failed to load when some transactions did not contain all requested fields, preventing users from viewing the transaction data. To fix the issue, MINT updated the search handler logic to allow ORD reports for ASN transaction data to complete successfully even when some transactions do not contain all requested field values. This issue has been resolved.
CMCP- 43305: Supplier ASN Line Items Could Not Be Deleted	Web UI	In MINT for Suppliers, added line items could not be removed from the Advance Shipment Notice (ASN) line item table when the transaction was opened for viewing or editing. To fix the issue, the line item table configuration was updated, and the Remove button now removes added line items as expected. This issue has been resolved.
CMCP-43411: Empty Rows Displayed in Stop Point and Shipment Information Tables	Web UI	In the Motor Carrier Load Tender transaction additional blank rows displayed in the Stop Point and Shipment Information table because required mapped attributes were not available in the MINT UI. To fix the issue, the rows are mapped correctly so that all required row details display as expected in the UI. This issue has been resolved.
CMCP- 43695: Line-Level Tax Information Not Mapped for Inbound Invoice	Web UI	The Inbound X12 Invoice transactions did not support mapping for the line-level TXI segment. As a result, tax information provided at the invoice line level was not captured through the standard inbound invoice processing flow. To fix the issue, the transform is updated to map the line-level TXI segment, enabling the transactions to retain and process tax information for each line item. This issue has been resolved.
CMCP- 43752: Sender or Receiver IDs Intermittently Missing in the MINT UI	Web UI	For some transaction workflows, sender or receiver IDs intermittently did not appear in the MINT UI due to a timeout while retrieving the associated network information. To fix the issue, MINT was updated to retry the request when a timeout occurs while retrieving network information. This helps ensure sender and receiver IDs are populated consistently in the MINT UI. This issue has been resolved.
CMCP- 44029: Party ID Values Missing from Copy Into Transactions	Web UI	MINT mappings did not extract alternate location identifiers for ship-to location details. As a result, Purchase Order Acknowledgments, Advance Shipment Notices, and Invoices created using Copy Into could contain empty Party ID fields when the primary location identifier was unavailable. To fix the issue, mapping logic is updated to use the alternate location identifier when the primary location identifier is unavailable. Party ID values now populate correctly in the MINT UI and downstream output files generated through the Copy Into action. This issue has been resolved.

Known issues

Multienterprise Information Network Tower, solution version 19.0.0

There are no known issues in this release.

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.

What's new in the user interface

Table of contents

What's new in Multienterprise Information Network Tower, solution version 19.0.0