What's new in the APIs
Type = What's New,; Topic = Multienterprise Information Network Tower (MINT),;Persona = Solution Designer, TraceLink Administrator, User, Orchestration Architect, Solution Partner, Technology Partner,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = Quality,
To learn more about what's new in the Multienterprise Information Network Tower, solution version 12.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 2024.7.0 app release, which is available on Validation on 13 Dec 2024 and Production on 27 Dec 2024.
The following apps are impacted by this release and will be updated to the version listed:
- Multienterprise Process Link, version 2024.7.0
Solutions supported by this app version:
- Multienterprise Information Network Tower, solution version 12.0.0
The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).
Download the PDF
This Help Center is subject to change based on the successful deployment of the release. In the event of changes, the Help Center will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.
Patch releases
The following patches are released for this version:
- Multienterprise Process Link, version 2024.7.2M1 is available on Validation and Production on 23 Jan 2025.
- Multienterprise Process Link, version 2024.7.2 is available on Validation and Production on 16 Jan 2025.
- Multienterprise Process Link, version 2024.7.1 is available on Validation and Production on 27 Dec 2024.
These patches are cumulative, and the most recent patch release includes functionality from all previous versions.
Revisions
| Date | Revision | Description |
|---|---|---|
| 21 Nov 2024 | 01 | Initial version. |
| 13 Dec 2024 | 02 | The following updates have been made since the previous revision was distributed:
|
| 27 Dec 2024 | 03 |
The following updates have been made since the previous revision was distributed:
|
| 16 Jan 2025 | 04 |
The following updates have been made since the previous revision was distributed:
|
| 23 Jan 2025 | 05 |
The following updates have been made since the previous revision was distributed:
|
API features
Multienterprise Process Link, version 2024.7.2M1
There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2024.7.2
There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2024.7.1
There is no new or updated API functionality included in this release.
Multienterprise Process Link, version 2024.7.0
Send and Receive Credit And Debit Adjustments in X12 and IDoc Formats
Companies that own or link to Multienterprise Process Link can exchange credit and debit adjustments with their Partners via TraceLink in X12 and IDoc formats. Credit and debit adjustments are bi-directions transactions which correct errors or make adjustments to previously recorded financial transactions of buyer or seller. In both cases, adjustments are made to the accounts receivable and payable ledger to reflect the corrected balances. For credit adjustments, the accounts receivable balance is decreased, indicating that the buyer owes less. Conversely, a debit adjustment increases the amount owed by a buyer. Exchanging credit and debit adjustments asynchronously via Multienterprise Process Link enhances the accuracy and efficiency of financial reconciliations and allows companies to manage discrepancies in invoices, payments, and inventory more effectively, leading to more accurate financial records and improved partner relationships.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot credit and debit adjustment messages; leverage a record of their credit and debit adjustment details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given credit and debit adjustment using the Search Business Transactions screen in the Multienterprise Information Network Tower Web UI.
The following new messages are available for sending or receiving credit and debit adjustments in this release:
- X12 (inbound):
- B2B_EDI_X12_812_CreditDebitAdjustment_IB_V1
- IDoc (outbound):
- B2B_IDoc_CREADV_PEXR2002_CreditDebitAdjustment_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Send and Receive Product Activities in X12 and IDoc Formats
Companies that own or link to Multienterprise Process Link can exchange product activities with their Partners via TraceLink in X12 and IDoc formats. Product activities refers to a centralized data set containing detailed and standardized information about a product or item. A product activity report is sent by the buyer to trading partners, suppliers, or stores to share inventory updates, helping suppliers plan shipments, propose replenishment quantities, and maintain proper inventory levels to reduce costs and improve ROI. This data serves as the foundation for managing logistics operations within the manufacturer’s ERP (Enterprise Resource Planning) or PIM (Product Information Management) system and shared by the buyer with the MAH to inform them of the product sold and remaining. Exchanging product activities asynchronously via Multienterprise Process Link enables companies to optimize key logistics functions, including warehouse management, transportation, and regulatory compliance.
Additionally, Multienterprise Process Link enables companies and their Partners to search for, view, and troubleshoot product activity messages; leverage a record of their product activity details for business records or compliance purposes; and retrieve the input, output, and canonical files for a given product activity 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 activities in this release:
- X12 (inbound):
- B2B_EDI_X12_852_ProductActivity_IB_V1
- IDoc (outbound):
- B2B_IDoc_PROACT_PROACT01_ProductActivity_OB_V1
Impact analysis
- Interface options:
- API
- Business segment impacts:
- All business segments for both Owners and Partners
Stabilization and usability enhancements
This feature streamlines usability with small enhancements, such as resubmitting a processed transaction and updating the Purchase Order Acknowledgment maps to include features required for customer implementations.
- Purchase Order Acknowledgment (inbound and outbound):
- B2B_EDI_X12_855_PurchaseOrderAcknowledgment_IB_V5
- B2B_EDI_X12_855_PurchaseOrderAcknowledgment_OB_V4
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
System features
Multienterprise Process Link, version 2024.7.2M1
There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2024.7.2
There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2024.7.1
There is no new or updated system functionality included in this release.
Multienterprise Process Link, version 2024.7.0
There is no new or updated system functionality included in this release.
Resolved issues
Multienterprise Process Link, version 2024.7.2M1
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| CMCP-38210: DELFOR SAP Control File Header Mapping Issue | API |
When a forecast transaction is sent in IDoc format, the DELFOR output file contains TraceLink's internal company SAP Control File Header values instead of the expected data. Although the location object is correctly configured, these values are not properly included in the DELFOR output message. Pre-Release Transform Name: B2B_IDoc_DELFOR_DELFOR02_ForecastPlan_OB_V2 This issue has been resolved. |
| TL-60846: Missing Shipment Extension Elements from STE in Shipment Event Map | API |
The transform MPC_STE_JSON_Canonical_SOM_ShipmentEvent_OB_V4 missing certain fields that might be useful in Serialized Operations Manager. This issue has been resolved. |
Multienterprise Process Link, version 2024.7.2
The following issue is resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| CMCP-38277: Store Number and Tax Segment Attributes Not Supported in PO and POAck Canonical | API |
PO and POAck canonical and it's subtypes do not map with store number and tax segments. This issue has been resolved. |
Multienterprise Process Link, version 2024.7.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-38095: Company's Location Unable to Retrieve Transaction in Outbox After Receipt | API |
In the Process Outbound state, the trigger for outbound BTO sends the parent company's network node ID (rootNetworkNodeId) as the receiverNetworkNodeId, resulting in the transaction being routed to the company's outbox. This issue has been resolved. |
| CMCP-38122: Transaction Processing Failure from Partner to Company Location | API |
Transaction initiated by partner to company location fails at processing stage with access denied message. This issue has been resolved. |
Multienterprise Process Link, version 2024.7.0
The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.
| ID | Interface | Issue Description |
|---|---|---|
| TL-52062: Unable to Reprocess Transactions After an Error is Encountered | API |
The user cannot resend transactions if the initial attempt encounters an error and fails to process successfully. This issue has been resolved. |
| TL-52574:Updated Assistive Text and Line Item Table | API |
The assistive text and line item table on View/Edit Pages for all transactions used a common text for both sender and receiver This issue has been resolved. |
| TL-53306: Delete Operation Enabled for Transactions in Sent State | API |
Delete operations is working even in states other than Draft. This issue has been resolved. |
| TL-56110: ASN OPUS Output not Matching with TTS Output | API |
Segments E1EDL41 and E1EDL43 in MINT output do not match with the TTS output for ASN. There are several fields missing in JSLT Maps. This issue has been resolved. |
| CMCP-37831: Partially Sent Transaction are Visible to Partners | API |
Transactions which are not in fully SENT status can be viewed on the Partner side. This issue has been resolved. |
| CMCP-37881: Resolved Transaction Error Handling for All Stages Except Conclude_Outbound | API |
Redelivering the transaction did not update the process status, which continued to display Error. This issue has been resolved. |
| CMCP-38030: Issues with Loading and Data Display on Business Transaction Page | API |
There is an inconsistency in handler versions, with the MPC handler (V1) being invoked for transactions initiated from the UI, while the TWR handler (V2) is triggered for transactions initiated via SFTP. This issue has been resolved. |
Known issues
Multienterprise Process Link, version 2024.7.2M1
There are no known issues in this release.
Multienterprise Process Link, version 2024.7.2
There are no known issues in this release.
Multienterprise Process Link, version 2024.7.1
There are no known issues in this release.
Multienterprise Process Link, version 2024.7.0
There are no known issues in this release.
Tag end
