What's new in the user interface

Explore what's new in the OPUS Track and Trace Lakehouse, solution version 1.0.0 release. To learn more about the OPUS Track and Trace Lakehouse Manager, version 2026.1.0 app that powers the solution, see What's new in the system.

Release information

This document describes the TraceLink capabilities included in the OPUS Track and Trace Lakehouse, solution version 1.0.0 release, which is available on Validation on 15 Oct 2026 and Production on 19 Nov 2026.

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

  • OPUS Track and Trace Lakehouse, solution version 1.0.0

    Apps that support this solution version:

    • OPUS Track and Trace Lakehouse Manager, version 2026.1.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.

Revisions

Date Revision Description
15 Oct 2026 01 Initial version.

UI features

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

Introduction to OPUS Track and Trace Lakehouse

This release introduces OPUS Track and Trace Lakehouse which is a reporting and analytics application that provides visibility into reconciled lot and serialization data across supply chain operations. OPUS Track and Trace Lakehouse presents structured reports for reviewing serial number status, lot activity, packaging relationships, locations, and transaction information. These reports help monitor serialized product activity, investigate discrepancies, and support reconciliation across operational workflows.

Using serialization and event-based data, OPUS Track and Trace Lakehouse helps analyze the current state and history of products and lots across the supply chain. The following are sample use cases:

  • Review serial number status by lot, location, or transaction
  • Analyze packaging hierarchies and parent-child relationships
  • Review serial number and lot event history
  • Reconcile lot activity and commissioned quantities
  • Investigate transaction and information exchange activity

Reports are configured in OPUS Reports and Dashboards and viewed in OPUS Track and Trace Lakehouse.

Serialization Analytics and Reporting

Users can use OPUS Track and Trace Lakehouse to access structured reports based on reconciled lot and serialization data. Each report organizes serialization events and related product, lot, location, packaging, and transaction information into focused views that support operational analysis and reconciliation.

The reports provide consistent visibility into:

  • Serial number status across lots, locations, and transactions
  • Packaging hierarchies and parent-child relationships
  • Lot and serial number event history
  • Commissioned quantities and reconciliation activity
  • Information exchange and transaction activity

Each report supports a specific operational or business need using serialization data. This helps users review product activity, investigate discrepancies, reconcile records, and monitor serialized supply chain operations more efficiently.

  • Commissioned Lot Quantities by Packaging Level – Provides total commissioned serial number quantities by item, lot, packaging code, packaging level, and commission location for the past six months. The report combines matching commission records into totals and includes product and target market details to support reconciliation with production, Level 3, or ERP data.

  • Info Exchange Messages – Provides processing and reconciliation statuses, transaction identifiers, sender and recipient details, file metadata, and error messages for Info Exchange messages updated in the past six months. These details support message tracing, investigation of failed or parked exchanges, and review of manually reconciled messages.

  • Lot Operation History – Provides the full recorded serialization, product verification, and EU compliance event history for packaging-code and lot combinations with activity in the past six months. Events from before that period are included to support operational investigations and troubleshooting.

  • Reconcile Lots – Identifies item and lot combinations with serialization activity in the past six months and a recorded commission event. The report provides details from each combination’s earliest commission event, including commission date, expiration date, product, target markets, and commission location, to support production reconciliation and follow-up investigations.

  • Serial Number Event History – Provides events recorded for an item and lot’s serial numbers, including event dates, types, locations, and reason codes. Transaction identifier filtering supports investigation of shipment, receipt, or other transaction activity, while unique commissioned serial number and event counts provide lot-level context.

  • Serial Number Hierarchy – Provides the current packaging hierarchy of serial numbers commissioned for an item and lot, including up to three parent-container levels and current serial number and item statuses. These details support reconciliation with Level 3 or ERP data and investigation of aggregation or repackaging discrepancies.

  • Serial Number Status by Location – Provides serial number counts by location, item, lot number, serial number status, and item status. The report uses each serial number's latest recorded event from the past 6 months. Users can filter the report by location and, optionally, lot number to reconcile data with operational systems and investigate discrepancies. For shipment and receipt events, the report uses the destination location.

  • Serial Number Status by Lot – Provides serial number counts by current serial number state and item status for an item and lot, based on each commissioned serial number’s latest recorded event. Counts are further separated by transaction, location, and reason code details to support review of the lot’s disposition and comparison with production or ERP records.

  • Serial Number Status by Transaction Identifier – Provides product and lot details with serial number counts by current serial number state and item status across transactions matching a selected identifier and type. Statuses are based on the latest recorded events within the past six months. Each serial number is counted once for the selected identifier and type, even when it appears in multiple matching transactions.

  • Serial Numbers and Commissioned Lot Quantities by Item – Provides each item’s unique commissioned lot total and commissioned serial number counts by packaging level for the past six months. These quantities support comparison with production or ERP records to identify discrepancies. The item’s lot total repeats across its packaging-level rows.

Additionally, users can also use the OPUS Track and Trace Lakehouse SQL tables to create custom reports in OPUS Reports and Dashboards (ORD). The tables provide access to Lakehouse serialization data, including event, product, lot, serial number, location, and transaction information.

Impact analysis

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

System features

There is no new or updated system functionality included in this release.

Resolved issues

OPUS Track and Trace Lakehouse, solution version 1.0.0

There are no resolved issues in this release.

Known issues

OPUS Track and Trace Lakehouse, solution version 1.0.0

There are no known issues in this release.