  

 

Orchestration Integration &amp; Transactions

 ## Breadcrumb

1. [Home](/)
2. [Orchestration Integration &amp; Transactions](/orchestration-integration-transactions)
 
  

 

 

# TL XML – SOM Aggregation Update

 

 

 

 

 

 ![banner-image](https://www.tracelink.com/sites/default/files/2024-02/For%20Internal%2066.png) 

 

 

 

 

#### Table of contents

 

 

 

### Overview

The SOM Aggregation Update transaction is an XML-based message used to record the aggregation of parent-child packaging relationships between serialized units (SGTINs) and containers (SSCCs). This transaction enables the creation, removal or reassignment of serialized units (SGTINs) within or between containers (SSCCs) to maintain accurate parent-child relationships in serialization records.

This transaction ensures that changes made to packaging hierarchies are traceable, compliant, and reflected across all connected systems. It supports DSCSA and global serialization regulations by preserving data integrity and enabling downstream visibility into product handling.

### Key Use Cases

- Document correct parent-child packaging relationships in serialization repositories between serialized product units and their containers.
- Remove serialized units from a case or pallet that require reinspection or rework.
- Improve operational efficiency during shipment, receipt, and inventory management processes by maintaining correct product identity relationships within containers that are scanned.
- Provide traceable, auditable records of packaging structure changes.
- Integrate with QA, warehouse, and serialization systems for real-time updates.

### Data Elements Included

A TL XML – SOM Aggregation Update transaction includes:

- **Transaction Type:** SOMAggregationUpdate
- **Parent Identifier:** SSCC of the case or pallet being updated.
- **Child Identifiers (EPCs):** SGTINs or SSCCs being added to or removed from the parent.
- **Action:** "add" or "delete" to indicate whether the relationship is being created or removed.
- **Event Timestamp:** Date and time the aggregation update occurred.
- **Read Point:** Location where the update was performed (e.g., QA station, warehouse).
- **Business Location:** GLN or internal identifier of the facility performing the update.
- **Disposition:** Optional field to indicate product state (e.g., "repacked").
- **Reason Code (optional):** Coded reason for the update (e.g., "QA\_REWORK").
- **Related Shipment or Batch ID (optional):** Links the update to a shipment or production batch.
- **Transaction ID (optional):** Unique identifier for the aggregation update event.
- **Digital Signature (optional):** Ensures data integrity and non-repudiation.
- **Comments or Notes (optional):** Free-text field for QA or operational context.

### Benefits of TL XML – SOM Aggregation Update

- Maintains accurate aggregation hierarchies.
- Prevents serialization mismatches in downstream processes.
- Supports regulatory compliance and audit readiness.
- Enables traceable rework and repackaging workflows.
- Reduces manual errors and enhances serialization data quality.

### Business Process: TL XML – SOM Aggregation Update

The SOM Aggregation Update transaction supports:

- Inventory Management: Reflects accurate container relationships for serialized inventory.
- Product Serialization &amp; Traceability: Maintains up-to-date parent-child packaging structures.
- Quality, Risk, and Recall Management: Tracks changes due to QA rework.
- Track and Trace &amp; Government Compliance: Ensures data integrity for serialization compliance.
- Returns and Reverse Logistics: Supports accurate handling of returns and repackaged units.

### How TraceLink Supports TL XML – SOM Aggregation Update

TraceLink’s OPUS Platform, powered by B2N Integrate-Once™, supports secure and compliant aggregation updates by:

- Capturing TL XML-compliant add/remove aggregation events with serialization context.
- Integrating with QA and warehouse systems to reflect real-time packaging updates.
- Logging all changes for traceability, audit readiness, and downstream reconciliation.
- Supporting exception handling and rework scenarios across global sites.
- Enabling secure communication with optional digital signatures and encryption.

### Explore More Serialization &amp; Compliance Capabilities

- [**TL XML – SOM Product Release**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release): Authorize serialized units.
- [**TL XML – SOM ESM Sales Shipment**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-esm-sales-shipment): Record serialized shipments.
- [**TL XML – SOM ESM Receipt**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-esm-receipt): Confirm serialized product receipt and verification.
- [**EPCIS 1.2 – SOM ESM Decommission**](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-decommission): Deactivate serialized units flagged for removal.

[See All Serialization and EPCIS Capabilities](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration)

### Need Help ImplementingTL XML?

[**Contact Us**](/contact-us) to learn how our OPUS Platform and B2N Integrate-Once™ model can help you manage aggregation updates, maintain serialization accuracy, and ensure compliance across your pharmaceutical supply chain.



 



 

 

 

#### Table of contents

 

 

 

Contact us to learn more about B2B Integration.

 

Fill out the form to contact us now.


    document.addEventListener("DOMContentLoaded", function() {
        // Delay the execution by 2 seconds (2000 milliseconds)
        setTimeout(function() {
            (function() {
                'use strict';
                // Load Marketo form
                MktoForms2.loadForm("//go.tracelink.com", "776-BAW-230", 2259);
            })();
            
            // Wait until the Marketo form is loaded
            MktoForms2.whenReady(function(form) {
                var formElement = document.getElementById('mktoForm_2259');
                if (!formElement) {
                    console.error("Form with id 'mktoForm_2259' not found.");
                    return;
                }
                
                var formLocation = formElement.querySelector("input[name=formLocation]");
                
                // Get the current URL and set the formLocation field
                if (formLocation) {
                    var currentURL = window.location.href;
                    formLocation.value = currentURL;
                }
                // Add onSuccess handler
                form.onSuccess(function(values, followUpUrl) {
                    var formElem = form.getFormElem()[0];
                    if (formElem) {
                        formElem.style.display = 'none';
                    } else {
                        console.warn("Form element could not be found to hide it.");
                    }
                    var confirmMessage = document.getElementById('confirmform');
                    if (confirmMessage) {
                        confirmMessage.style.display = 'block';
                    } else {
                        console.warn("Confirmation message with id 'confirmform' not found.");
                    }
                    
                    return false;  // Prevent the form from submitting normally
                });
            });
        }, 2000);  // Delay for 2 seconds
    });
**Thank you for contacting us; we’ll be in touch shortly.**





 

 

 

 

 

 

 

##### Related Content

 

 [ ![wholesale distributor](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-03/wsd-2.png.webp?itok=Q0nGUO1Y) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-hda-advance-ship-notice) 

#####  EPCIS 1.2 – HDA Advance Ship Notice 

 The EPCIS 1.2 – HDA ASN (Advance Ship Notice) is an XML-based electronic message that provides detailed, serialized shipment information from pharmaceutical manufacturers or distributors to downstream trading partners in compliance with Healthcare Distribution Alliance (HDA) and DSCSA (Drug Supply Chain Security Act) guidelines. 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-hda-advance-ship-notice) 

 

 [ ![CMO](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/LifeScience-CMO8%20%281%29.png.webp?itok=3ZnAZMLd) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-dscsa-advance-ship-notice) 

#####  EPCIS 1.2 – DSCSA Advance Ship Notice 

 The EPCIS 1.2 – DSCSA ASN (Advance Ship Notice) is an XML-based electronic message used to transmit serialized product shipment data in compliance with the Drug Supply Chain Security Act (DSCSA). 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-dscsa-advance-ship-notice) 

 

 [ ![Wholesale-Distributor](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/For%20Internal%2055.png.webp?itok=0K8agZX1) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-serialization) 

#####  EPCIS 1.2 – Serialization 

 The EPCIS 1.2 – Serialization transaction is an XML-based message used to capture and share commissioning (serialization) events for pharmaceutical products. 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-serialization) 

 

 [ ![Brazil Pharmaceuticals](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/LifeScience%20CMO-1.png.webp?itok=8qEXci20) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-update-lot-information) 

#####  EPCIS 1.2 – SOM ESM Update Lot Information 

 The EPCIS 1.2 – SOM ESM Update Lot Information transaction is an XML-based message used to update or correct lot-level information for serialized pharmaceutical products. 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/epcis-12-som-esm-update-lot-information) 

 

 [ ![crypto code](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2024-02/crypto%20code.png.webp?itok=hDYDa49u) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-receipt) 

#####  TL XML – SOM Receipt 

 The SOM Receipt transaction is an XML-based message used to record the receipt and transfer serialized products between warehouses and trading partners. 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-receipt) 

 

 [ ![digitalising order management](https://www.tracelink.com/sites/default/files/styles/resize_image_style_640_480/public/2025-04/GettyImages-1299660112.jpg.webp?itok=qNA8FTp4) ](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release) 

#####  TL XML – SOM Product Release 

 The SOM Product Release transaction is an XML-based message used to indicate that a serialized pharmaceutical product or batch has successfully passed quality review and other product release processes and is now authorized for downstream processing—such as shipment, aggregation, or inventory movement. 

 

 [View More](/orchestration-integration-transactions/accelerate-digital-supply-chain-collboration-with-b2b-integration/tl-xml-som-product-release)