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 informationThis 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.6Solutions supported by this app version:
Multienterprise Information Network Tower, solution version 11.0The 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 releasesThe 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 02The 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 04The 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.0M1The following new or updated API functionality is included in this release.
Enhancements to Existing Invoice and Forecast Plan MessagesThe 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.0The 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 ReleaseThe 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) MessagesThe 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 FormatCompanies 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 FormatsCompanies 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_V1Impact 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 FormatsCompanies 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_V1Impact 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 FormatsCompanies 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_V1Impact analysis
Interface options: API Business segment impacts:All business segments for both Owners and Partners Enhancements to Existing MessagesA 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_V3Additionally, 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.0M1There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2024.6.0There is no new or updated system functionality included in this release.
Resolved issues Multienterprise Process Link, version 2024.6.0M1The 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 UIThe 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.0There are no resolved issues in this release.
Known issues Multienterprise Process Link, version 2024.6.0M1There are no known issues in this release.
Multienterprise Process Link, version 2024.6.0There are no known issues in this release.
&source=TraceLink "LinkedIn") - [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/whats-new-multienterprise-process-link-version-20246&t=What's new in Multienterprise Process Link, version 2024.6 "Facebook") - [ Mail ](mailto:?subject=What's new in Multienterprise Process Link, version 2024.6+|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/whats-new-multienterprise-process-link-version-20246 "Mail") - [ Twitter ](https://twitter.com/intent/tweet?text=What's new in Multienterprise Process Link, version 2024.6 https://www.tracelink.com/resources/tracelink-university/whats-new-multienterprise-process-link-version-20246&via=TraceLink "Twitter") #### Table of contents 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.6Solutions 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\_V2 - B2B\_EDI\_EDIFACT\_INVOIC\_Invoice\_IB\_V3 - B2B\_EDI\_EDIFACT\_INVOIC\_Invoice\_OB\_V2 - B2B\_EDI\_X12\_810\_Invoice\_IB\_V4 - B2B\_EDI\_X12\_810\_Invoice\_OB\_V2 - B2B\_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\_V3 - B2B\_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\_V2 - B2B\_EDI\_X12\_810\_Invoice\_IB\_V4 - B2B\_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\_V2 - B2B\_EDI\_X12\_856\_AdvanceShipNotice\_IB\_V2 - B2B\_EDI\_EDIFACT\_DESADV\_AdvanceShipNotice\_IB\_V2 - Batch transforms - B2B\_IDoc\_BATMAS\_BATMAS03\_BatchMaster\_IB\_V2 - Forecast transforms: - B2B\_IDoc\_DELFOR\_DELFOR02\_ForecastPlanResponse\_IB\_V2 - B2B\_IDoc\_DELFOR\_DELFOR02\_ForecastPlan\_OB\_V2 - Inventory Balance & Inventory Update transforms: - B2B\_IDoc\_INVRPT\_INVRPT01\_InventoryBalance\_IB\_V2 - B2B\_EDI\_X12\_846\_InventoryBalance\_IB\_V2 - B2B\_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 transforms - B2B\_IDoc\_ORDERS05\_PurchaseOrder\_IB\_V4 - B2B\_EDI\_X12\_850\_PurchaseOrder\_IB\_V3 - B2B\_EDI\_EDIFACT\_ORDERS\_PurchaseOrder\_IB\_V3 - B2B\_IDoc\_ORDERS05\_PurchaseOrderAcknowledgment\_IB\_V3 - B2B\_EDI\_X12\_855\_PurchaseOrderAcknowledgment\_IB\_V3 - B2B\_EDI\_EDIFACT\_ORDRSP\_PurchaseOrderAcknowledgment\_IB\_V2 - Remittance Advice transforms: - B2B\_IDoc\_REMADV\_PEXR2003\_RemittanceAdvice\_OB\_V2 - B2B\_EDI\_X12\_820\_RemittanceAdvice\_IB\_V2 - Warehouse Shipping Advice transforms - B2B\_IDoc\_SHPCON\_DELVRY07\_ShipAdvice\_IB\_V2 - B2B\_EDI\_X12\_945\_WHS\_ShipAdvice\_IB\_V3 - Warehouse Shipping Order transforms - B2B\_IDoc\_SHPORD\_DELVRY03\_ShipOrder\_IB\_V2 - B2B\_EDI\_X12\_940\_WHS\_ShipOrder\_IB\_V2 - Warehouse Stock Transfer Shipment Advice transforms - B2B\_IDoc\_WMTORD\_WMTOID02\_WHS\_StockTransferShipAdvice\_IB\_V2 - B2B\_EDI\_X12\_943\_WHS\_StockTransferShipAdvice\_IB\_V2 - Warehouse Stock Transfer Receipt Advice - B2B\_IDoc\_WMTOCO\_WMTCID03\_WHS\_StockTransferReceiptAdvice\_IB\_V2 - B2B\_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. #### Table of contents ##### Related Content [  ](/resources/tracelink-university/extensible-tracelink-transfer-version-20243) ##### Extensible TraceLink Transfer, version 2024.3 To learn more about what's new in the Extensible TraceLink Transfer, solution version 5.0 that provides the user interface for this app, see What's new in the user interface. [View More](/resources/tracelink-university/extensible-tracelink-transfer-version-20243)