Search deliveries

US Compliance provides the original delivery details for shipments and receipts from the US target market as they are passed from the US Compliance Owner's instance of Serialized Operations Manager or received in a US Product Track GS1 US Healthcare Transaction History (EPCIS v1.2) message, in case companies need to troubleshoot problems with the delivery or retrieve the original delivery details during an audit. US Compliance also uses these deliveries to generate transaction information and transaction statement (T2) documents.

Filter and view deliveries

  1. Select the Main Menu icon.
  2. Select My Networks or Partner Networks depending on the desired network.

  3. Select a Network in the header.

  4. Select a Partner or Location (e.g. your entire company or a Link to a specific Partner or internal location) in the header.
  5. Select the Go button.
  6. Select Search from the Deliveries drop-down in the side menu.
  7. Fill in one or more of the following fields to filter the results:
    1. Date Shipped field – The date range for when the delivery was shipped.
    2. Delivery Number field – The delivery number associated with the shipment or receipt.
    3. Transaction ID, Lot Number, or Entity field – The transaction ID value, lot number, business or location name, or business or location identifier value associated to the delivery.
  8. Select Show Additional Filters and fill in the following fields to further filter the results:
    1. Filter By drop-down – The type of value to filter for:
      1. Delivery Type – The type of delivery:
        • All
        • Shipment – The delivery is an outbound shipment from your company to another entity.
        • Receipt – The delivery is an inbound receipt that your company received from another entity.
      2. Status – The status of the message communicating the delivery:
        • All
        • Generated – TraceLink generated the delivery, but it has not yet been sent to the recipient.
        • Delivered – TraceLink generated the delivery, and it was successfully sent to the recipient.
        • Generation Failed – The delivery could not be generated, either because the message failed to map in to TraceLink or failed processing.
        • Delivery Failed – TraceLink generated the delivery, but it could not be sent to the recipient, either because it failed to map out to the recipient or there was an error.
        • Voided – A previously submitted delivery that is canceled or invalidated.
      3. Item Code – The item code that identifies the product, usually an NDC.
        For accurate search result, the Item Code for the product must match the same format as entered in the Order Items on the delivery in the sender's Serialized Operations Manager. For example, if the Order Items on the delivery has hyphens (-), the Item Code for the product must also have hyphens in it.
      4. Lot Number – The lot number for the serialized items.
      5. Packaging Code – The packaging code for the product.
      6. Transaction ID – The transaction identifiers associated to the delivery (e.g. Purchase Order Number).
      7. From Business – The business that ships the delivery.
      8. To Business – The business that receives the delivery.
      9. Ship From Location – The physical location that the delivery is shipped from.
      10. Ship To Location – The physical location that receives the delivery.
    2. Select Add Another Filter to specify another Filter Option.

      Select the Remove icon to remove filter criteria.

  9. Select Apply.

    The results display in the table.

    • Status – The status of the message communicating the delivery:
      • Generated – TraceLink generated the delivery, but it has not yet been sent to the recipient.
      • Delivered – TraceLink generated the delivery, and it was successfully sent to the recipient.
      • Generation Failed – The delivery could not be generated, either because the message failed to map in to TraceLink or failed processing.
      • Delivery Failed – TraceLink generated the delivery, but it could not be sent to the recipient, either because it failed to map out to the recipient or there was an error.
      • Voided – A previously submitted delivery that is canceled or invalidated.
    • Date Shipped – The date that the delivery was shipped.
    • Delivery Type – The type of delivery:
      • Shipment – The delivery is an outbound shipment from your company to another entity.
      • Receipt – The delivery is an inbound receipt that your company received from another entity.
    • From Business – The business that ships the delivery.
    • To Business – The business that receives the delivery.
    • Ship To Location – The physical location that the delivery is shipped from.
    • Transaction IDs – The transaction identifiers associated to the delivery (e.g. Purchase Order Number).
    • Quantity – The number of serialized items in the delivery.
  10. Select the View icon for a specific delivery.

    The View Delivery screen displays. See Delivery details for more information.

Tips

  • Select the Export Search Results in CSV icon to export all of the deliveries in the results to a CSV file.
  • Select View T2 Documents on any row to view the list of T2 documents generated for that delivery.
  • Select the View icon for a row with Voided Status to view a specific voided delivery. When selected, the View Voided Delivery screen displays. See Voided delivery details for more information.
  • Select any row to display a panel with additional information about the delivery.

Configure the delivery

On Track & Trace Services

Some of the event triggers (i.e. event workflows on Track & Trace Services) for US Compliance, that happen in Serialized Operations Manager, are still set in Track & Trace Services Company Administration. Make sure one of the following event triggers are enabled:

Event Workflow Resulting Action Recipient System Description
Product Shipped - Sale Generate Shipment EPCIS Message US Product Track TraceLink generates a message to the Product Track Service to create the EPCIS Shipment message containing the commissioning, aggregation and shipment EPCIS events for the serialized items associated with the shipment. This message will be generated after TraceLink has processed the receipt of a Sales Shipment message from Serialized Operations Manager for outbound deliveries that have a Ship To Country Code set to US.

ESM Product Shipped - Sale

 Generate Shipment EPCIS Message US Product Track TraceLink generates an EPCIS Shipment message containing the commissioning, aggregation and shipment EPCIS events for the serialized items associated with the shipment. This message will be generated after TraceLink has processed the receipt of an ESM Shipment Event message from Serialized Operations Manager for outbound deliveries that have a Ship To Country Code set to US.
Void Shipment - Sale Send SOM Void Shipment Message US Compliance TraceLink sends the SOM Void Shipment message where the Sales Distribution Type is an In Country Sale or Export Sale and the Ship To Country is set to US or its territories.
ESM Void Shipment - Sale Send SOM ESM Void Shipment Message US Compliance TraceLink sends the SOM ESM Void Shipment message where the Sales Distribution Type is an In Country Sale or Export Sale and the Ship To Country is set to US or its territories.
Void Receipt - Sale Send SOM Void Receipt Message US Compliance TraceLink sends the SOM Void Receipt message where the Sales Distribution Type is an In Country Sale or Export Sale and the Ship To Country is set to US or its territories.
ESM Void Receipt - Sale Send SOM ESM Void Receipt Message US Compliance TraceLink sends the SOM ESM Void Receipt message where the Sales Distribution Type is an In Country Sale or Export Sale and the Ship To Country is set to US or its territories.

For more information on how to enable the event triggers, see the Company Administration Online Help.

On the Opus Platform

The event triggers (i.e. workflow subscriptions) for US Compliance, that happen in the Opus platform, can be set in Administer.

Source Application Event Action Description
US Product Track T2 Generated Generate Shipment Notices for Indirect Trade Partners Tracelink generates and sends a shipment notice to Product Information Manager to enable indirect trade partners access to the shipment notice, if the Enabled switch is set to Yes for this workflow subscription.
US Product Track T2 Generated Generate Shipment Notices for Direct Trade Partners Not Linked to US Compliance Tracelink generates and sends a shipment notice to Product Information Manager to enable access for direct trade partners who are not linked to US Compliance to access the shipment notice, if the Enabled switch is set to Yes for this workflow subscription.

Shipments

US Compliance generates shipments when TraceLink processes a Product Shipped - Sale or ESM Product Shipped - Sale event and all of the following conditions are met:

  • The shipment's Sale Type is Sale - In Country or Sale - Export.
  • The Ship To Country is United States.
  • The shipment includes at least one PO, ASN, or Invoice Transaction ID.
  • The shipment specifies the identifier, name, and address for the From Business, To Business, Ship From Location, and Ship To Location.
  • The products in the shipment have both a 10-digit and an 11-digit NDC present in Product Master Data (i.e. a US - NDC442, US - NDC532, or US - NDC541 and a US - NDC542).

The shipment notices for these receipts are then sent to Product Information Manager for indirect trade partners to access when the Generate Shipment Notices for Indirect Trade Partners workflow subscription in Opus Administer is enabled, and if the original shipment:

  • Is marked as a Drop Shipment.
  • Includes a Portal Access Code.

The shipment notices are also sent to Product Information Manager for direct trade partners to access when the Generate Shipment Notices for Direct Trade Partners Not Linked to US Compliance workflow subscription in Opus Administer is enabled, and if the original shipment:

  • Specifies a To Business that is not linked to the Owner's US Compliance network.
  • Is not marked as a Drop Shipment.
  • Includes a Portal Access Code.

Receipts

US Compliance generates receipts when the company receives a US Product Track GS1 US Healthcare Transaction History (EPCIS v1.2) message, which is triggered when a shipment is generated. See the US Product Track API Guide for more information.

Shipment notices are also sent to US Product Track when the indirect trade partners (e.g. Dispensers) who receive the shipment notice are linked to Product Information Manager and own US Product Track as well as Serialized Operations Manager. US Product Track then sends these notices to US Compliance so that the indirect trade partner does not need to use the Product Information Manager Web UI at all if they do not want to. US Compliance uses these shipment notices to generate receipts and T2 documents.

Generate the delivery

To generate the delivery in US Compliance automatically, enable the appropriate event triggers and ensure that the relevant event trigger conditions are met. When configured, US Compliance generates the delivery automatically when the following events occur in one of these interfaces:

Use any of the following Serialized Operations Manager APIs to trigger shipments:

Receiving the US Product Track GS1 US Healthcare Transaction History (EPCIS v1.2) message triggers receipts.

ESM Shipment (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager ESM Synchronization API Guide for more information.

Element Values
VocabularyElement

Must include:

  • A ship from location with a name, address, and identifier.
  • A ship to location with a name, address, and identifier.

If the to business is not linked to the Owner's US Compliance network and a tl:portalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.

bizTransactionList

Must include at least one transaction ID with one of the following types:

  • urn:epcglobal:cbv:btt:po – Purchase Order Number.

  • urn:epcglobal:cbv:btt:desadv – Advanced Shipment Notice.

  • urn:epcglobal:cbv:btt:inv – Invoice.
tl:shipToCountryCode US.
tl:saleDistributonType INCOUNTRYSALE or EXPORTSALE.
tl:dropShipmentIndicator

To send the shipment notice to Product Information Manager, specify true.
tl:portalAccessCode

To send the shipment notice to Product Information Manager, specify the portal access code.

ESM Shipment (XML)

Complete the elements required for the report as follows. See the Serialized Operations Manager ESM Synchronization API Guide for more information.

Element Values
cmn:TransactionIdentifier

Must include at least one transaction ID with one of the following types:

  • PO – Purchase Order Number.
  • ASN – Advanced Shipment Notice.
  • INVOICE – Invoice.
cmn:shipToCountryCode US.
cmn:saleDistributonType INCOUNTRYSALE or EXPORTSALE.
cmn:DropShipment To send the shipment notice to Product Information Manager, specify true.
cmn:PortalAccessCode To send the shipment notice to Product Information Manager, specify the portal access code.
cmn:ShipFromLocationLookupId or cmn:ShipFromLocationInfo

Specify a ship from location. For cmn:ShipFromLocationInfo, include the name and address.
cmn:ReceiverInfo

If the to business is not linked to the Owner's US Compliance network and a cmn:PortalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

cmn:ShipToLocationLookupId or cmn:ShipToLocationInfo

Specify a ship to location. For cmn:ShipToLocationInfo, include the name and address.

Sales Shipment (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager Core Integration API Guide for more information.

Element Values
VocabularyElement

Must include:

  • A ship from location with a name, address, and identifier.
  • A ship to location with a name, address, and identifier.

If the to business is not linked to the Owner's US Compliance network and a tl:portalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.

bizTransactionList

Must include at least one transaction ID with one of the following types:

  • urn:epcglobal:cbv:btt:po – Purchase Order Number.

  • urn:epcglobal:cbv:btt:desadv – Advanced Shipment Notice.

  • urn:epcglobal:cbv:btt:inv – Invoice.
tl:shipToCountryCode US.
tl:saleDistributonType INCOUNTRYSALE or EXPORTSALE.
tl:dropShipmentIndicator

To send the shipment notice to Product Information Manager, specify true.
tl:portalAccessCode

To send the shipment notice to Product Information Manager, specify the portal access code.

Sales Shipment (XML)

Complete the elements required for the report as follows. See the Serialized Operations Manager Core Integration API Guide for more information.

Element Values
cmn:TransactionIdentifier

Must include at least one transaction ID with one of the following types:

  • PO – Purchase Order Number.
  • ASN – Advanced Shipment Notice.
  • INVOICE – Invoice.
cmn:shipToCountryCode US.
cmn:saleDistributonType INCOUNTRYSALE or EXPORTSALE.
cmn:DropShipment To send the shipment notice to Product Information Manager, specify true.
cmn:PortalAccessCode To send the shipment notice to Product Information Manager, specify the portal access code.
cmn:ShipFromLocationLookupId or cmn:ShipFromLocationInfo

Specify a ship from location. For cmn:ShipFromLocationInfo, include the name and address.
cmn:ReceiverInfo

If the to business is not linked to the Owner's US Compliance network and a cmn:PortalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

cmn:ShipToLocationLookupId or cmn:ShipToLocationInfo Specify a ship to location. For cmn:ShipToLocationInfo, include the name and address.

Shipment Event (EPCIS v1.2)

Complete the elements required for the report as follows. See the Serialized Operations Manager Trade Partner Event Exchange API Guide for more information.

Element Values
VocabularyElement

Must include:

  • A ship from location with a name, address, and identifier.
  • A ship to location with a name, address, and identifier.

If the to business is not linked to the Owner's US Compliance network and a tl:portalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

The locations can also be specified in the sourceList or destinationList for the shipment event as a master data lookup.

bizTransactionList

Must include at least one transaction ID with one of the following types:

  • urn:epcglobal:cbv:btt:po – Purchase Order Number.

  • urn:epcglobal:cbv:btt:desadv – Advanced Shipment Notice.

  • urn:epcglobal:cbv:btt:inv – Invoice.
tl:shipToCountryCode US.
tl:saleDistributonType INCOUNTRYSALE or EXPORTSALE.
tl:dropShipmentIndicator

To send the shipment notice to Product Information Manager, specify true.
tl:portalAccessCode

To send the shipment notice to Product Information Manager, specify the portal access code.

Update Order Shipment (SOAP)

Complete the elements required for the report as follows. See the Serialized Operations Manager SOAP API Guide for more information.

Element Values
ShipToCountryCode US.
SaleType INCOUNTRYSALE or EXPORTSALE.
Transactions

Must include at least one transaction ID with one of the following types:

  • PO – Purchase Order Number.
  • ASN – Advanced Shipment Notice.
  • INVOICE – Invoice.
ShipFromLocation

Specify a ship from location.
SoldToParty

If the to business is not linked to the Owner's US Compliance network and a portalAccessCode is included, the corresponding shipment notice is sent to Product Information Manager.

ShipToLocation Specify a ship to location.
DropShipment To send the shipment notice to Product Information Manager, specify true.
portalAccessCode To send the shipment notice to Product Information Manager, specify the portal access code.

GS1 US Healthcare Transaction History (EPCIS v1.2)

No specific values are required to trigger the shipment notice generated from this message. See the US Product Track API Guide for more information.

Use Serialized Operations Manager to trigger the shipments from the Web UI. See the Serialized Operations Manager Online Help for more information.

  1. In Track & Trace Services, hover over Modules, and then select Serialized Operations Manager.
  2. Expand the Outbound Movement drop-down, and then select Create Delivery.
  3. Select the manufacturing location that provisioned the serial numbers from the Show Data From drop-down in the upper right.
  4. Complete the fields required for the report as follows:
    ElementValues
    Sale TypeSale - In Country or Sale - Export.
    Ship To Country CodeUS.
    To Business

    If the to business is not linked to the Owner's US Compliance network and a Portal Access Code is included, the corresponding receipt is sent to Product Information Manager.

    Ship From Location

    Specify a ship from location.

    Ship To Location Specify a ship to location.
    Drop ShipmentTo send the shipment notice to Product Information Manager, select the checkbox.
    Portal Access CodeTo send the shipment notice to Product Information Manager, specify the portal access code.
    Transaction IDs

    Must include at least one transaction ID with one of the following types:

    • PO Number – Purchase Order Number.
    • Shipment Number – Advanced Shipment Notice.
    • Invoice Number – Invoice.
  5. Complete any other fields that are required in the UI or that your company uses for a specific purpose.
  6. Select Submit.

    The View Deliveries screen displays, the shipment is added, and:

    1. Serialized Operations Manager sends the GS1 US Healthcare Transaction History (EPCIS v1.2) message to US Product Track.
    2. US Compliance generates a shipment for the delivery.
    3. US Product Track sends the EPCIS v1.2 message to the Partner receiving the delivery, and US Compliance creates a shipment notice for the Partner.

Use Smart Inventory Tracker to trigger the shipment from a mobile device. See the Smart Inventory Tracker Help Center for more information.

  1. In the Smart Inventory Tracker mobile app, do one of the following:
    • Ship product with an existing delivery number. The delivery number must already exist in Serialized Operations Manager with the fields required for the shipment.
    • Create a new delivery to ship product.
  2. If creating a new delivery in Smart Inventory Tracker, complete the following steps:

    Create a new delivery in Smart Inventory Tracker only if the shipment notice does not need to be sent to Product Information Manager.

    1. Complete the fields required for the report as follows:
      ElementValues
      Sale TypeSale - In Country or Sale - Export.
      Ship To CountryUS.
      Ship From Location

      Specify a ship from location.

      Ship To LocationSpecify a ship to location.
      Transaction ID

      Must include at least one transaction ID with one of the following types:

      • PO Number – Purchase Order Number.
      • Shipment Number – Advanced Shipment Notice.
      • Invoice Number – Invoice.
    2. Complete any other fields that are required in the UI or that your company uses for a specific purpose.
  3. Select Submit.

    Smart Inventory Tracker takes the resulting action, and:

    1. Serialized Operations Manager sends the GS1 US Healthcare Transaction History (EPCIS v1.2) message to US Product Track.
    2. US Compliance generates a shipment for the delivery.
    3. US Product Track sends the EPCIS v1.2 message to the Partner receiving the delivery, and US Compliance creates a shipment notice for the Partner.

Currently, deliveries cannot be manually generated in US Compliance. If there is a problem with the delivery in Serialized Operations Manager or the US Product Track GS1 US Healthcare Transaction History (EPCIS v1.2) message, see Info Exchange on Track & Trace Services to correct the issues and reprocess the message. When the message is reprocessed with the correct information, US Compliance will generate the delivery.

Delivery details

  • Status – The status of the message communicating the delivery:
    • Generated – TraceLink generated the delivery, but it has not yet been sent to the recipient.
    • Delivered – TraceLink generated the delivery, and it was successfully sent to the recipient.
    • Generation Failed – The delivery could not be generated, either because the message failed to map in to TraceLink or failed processing.
    • Delivery Failed – TraceLink generated the delivery, but it could not be sent to the recipient, either because it failed to map out to the recipient or there was an error.
    • Voided – A previously submitted delivery that is canceled or invalidated.
  • Processing Time – The date and time that the message was processed.
  • Input File – The original file that was sent to TraceLink.
  • Output File – The file that TraceLink processed and sent to the receiving party.
  • Canonical File – The file in TraceLink that was used as the source of truth to process the input file into the output file.
  • Log File – The log file for the delivery message.
  • Void File – The void file for the delivery message.

Tips

  • Select the Input File, Output File, Canonical File, Log File, or Void File link to download the raw message file.

Displays only for deliveries with a Status of Voided.

  • Reason – The reason for voiding the delivery:

    • Correction – A user entered incorrect information when creating or receiving the shipment.

    • Damaged – The product is damaged.

    • Damaged in Facility – The product was damaged in the facility.

    • Damaged in Transit – The product was damaged during transit.

    • Data Issue – TraceLink contains incorrect data.

    • Destroyed – The product was destroyed.

    • Expired – The product expired.

    • Found Inventory – A user found product that does not exist in the inventory.

    • Investigation – The product could be damaged, so someone must test the product (e.g. because of a temperature excursion).

    • Lost Inventory – The product is missing.

    • Order Cancelled – The shipment order was canceled.

    • Order Rejected – The shipment order was rejected.

    • Other – The product needs to be updated for a reason not listed here.

    • Over Receipt – A user at the receiving location found more product in the shipment than the receipt had listed.

    • Over Ship – A user at the shipping location realized the shipment contains more product than the receipt had listed.

    • Physical Count – The inventory needs to be updated after performing a physical count of the inventory.

    • Recalled – The product was recalled.

    • Receiving Error – A user made an error when receiving the shipment in TraceLink.

    • Shipping Error – A user made an error when creating the shipment in TraceLink.

    • Short Receipt – A user at the receiving location found less product in the shipment than the receipt had listed.

    • Short Ship – A user at the shipping location realized the shipment contains less product than the receipt had listed.

  • Date Voided – The date and time the delivery was voided, in the format DD MMM YYYY. This field corresponds to the Transaction Date specified by the user in Serialized Operations Manager.
  • Comments – Descriptive text explaining the reason for the voided delivery.
  • Processing Time – The void date of the delivery within TraceLink. This field corresponds to the Date Voided field in Serialized Operations Manager.
Field Description Sourced From
Delivery Number The delivery number associated to the shipment or receipt. The Delivery Number for the delivery in the sender's Serialized Operations Manager.
Date Shipped The date that the delivery was shipped. The Shipment Date for the delivery in the sender's Serialized Operations Manager.
Transaction IDs The transaction identifiers associated to the delivery (e.g. Purchase Order Number). The Transaction IDs for the delivery in the sender's Serialized Operation Manager.
Delivery Type The type of delivery:
  • Shipment – The delivery is an outbound shipment from your company to another entity.
  • Receipt – The delivery is an inbound receipt that your company received from another entity.
See the event trigger conditions for more information about whether the delivery displays as a Shipment or Receipt.
From Business The business that ships the delivery.

The From Business for the delivery in the sender's Serialized Operation Manager.
To Business The business that receives the delivery.

The To Business for the delivery in the sender's Serialized Operation Manager.
Ship From Location The physical location that the delivery is shipped from.

The Ship From Location for the delivery in the sender's Serialized Operation Manager.
Ship To Location The physical location that receives the delivery.

The Ship To Location for the delivery in the sender's Serialized Operation Manager.
View Aggregation Hierarchy The link to view the aggregation hierarchy for a serialized delivery. After selecting the link, TraceLink retrieves the aggregation hierarchy and displays the information after some time. See the Aggregation Hierarchy table for more information.
Field Description Sourced From
Item Code The item code that identifies the product, usually an NDC.

The Item Code for the product, as entered in the Order Items on the delivery in the sender's Serialized Operations Manager.

Product Name

The name of the product.

The Product Name in the sender's Product Master Data.
Product Description The description of the product, which typically includes the strength, dose, and other product information. The Product Description in the sender's Product Master Data.
Lot Number The lot number for the serialized items.

The lot number in the sender's Serialized Operations Manager for this product's serialized items.
Expiration Date The expiration date for the serialized items.

The expiration date in the sender's Serialized Operations Manager for the serial numbers in this lot.
Quantity

The number of serialized items for this product and lot number combination on the delivery.

The number of serialized items for this product and lot number combination added to the delivery in the sender's Serialized Operations Manager.
Traceability Required

Indicates whether the product must be traced through the supply chain by law:

  • Yes – The product must be traced, as required by the DSCSA.
  • No – The product does not need to be traced, as defined by the DSCSA (e.g. over the counter medication).

The Traceability Required value in the product's US target in the sender's Product Master Data.

Tips

  • Select the Export icon to export the serial numbers in the delivery as a CSV file.
    • Serial Number – The serial number of the item.
    • Parent Serial Number – The parent serial number of the Serial Number.
    • Item Code Type – The type of item code (not including an Internal Material Number). See Identifier and Item Code Types for more information.
    • Item Code – The value of the item code.
    • Packaging Code Type – The type of packaging code for the serial number, based on its packaging level (e.g. each, case).
    • Packaging Code – The value of the packaging code.
    • Lot Number – The lot number for the Serial Number.
    • Expiration Date – The expiration date for the Serial Number.

The Web UI can only display up to 500 serial numbers. If the delivery contains more than 500 serial numbers, export the full aggregation hierarchy to view additional serial numbers.

  • Serial Number – The serial number for that specific serialized unit in the delivery. If there is no aggregation, the Serial Number represents the each-level serial number.
  • Item Code – The item code that identifies the product, usually an NDC.Displays as -- for SSCC serial numbers.
  • Description – The description of the product, which typically includes the strength, dose, and other product information. Displays as -- for SSCC serial numbers.
  • Lot Number – The lot number for the serialized items.
  • Expiration Date – The expiration date for the serialized items.
  • Additional Statement – Where the product originated:
    • Direct Purchase – The seller made a direct purchase from the Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.
    • Received Direct Purchase – The seller purchased the product from a Wholesale Distributor who made a direct purchase from the Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.
    • -- – The seller is the Pharmaceutical Manufacturer, Exclusive Distributor, Repackager, or the seller originally purchased the product from a Wholesale Distributor who did not make a direct purchase from a Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.

Tips

  • Select the View icon on any row to view information about the Serial Number and its children.

    Parent Container

    • Serial Number – The parent serial number for that specific serialized unit in the delivery. Select the Serial Number link to return to the previous aggregation level.
    • Container Hierarchy – The hierarchy level of the parent container for this serialized unit. A Level 1 container is the top-level or outermost serialized content, a Level 2 container is a child of a top-level serialized container, and so forth.

    Aggregation Hierarchy

    • Serial Number – The serial number for that specific serialized unit in the delivery. If there is no aggregation, the Serial Number represents the each-level serial number.
    • Item Code – The item code that identifies the product, usually an NDC.Displays as -- for SSCC serial numbers.
    • Description – The description of the product, which typically includes the strength, dose, and other product information. Displays as -- for SSCC serial numbers.
    • Lot Number – The lot number for the serialized items.
    • Expiration Date – The expiration date for the serialized items.
    • Additional Statement – Where the product originated:
      • Direct Purchase – The seller made a direct purchase from the Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.
      • Received Direct Purchase – The seller purchased the product from a Wholesale Distributor who made a direct purchase from the Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.
      • -- – The seller is the Pharmaceutical Manufacturer, Exclusive Distributor, Repackager, or the seller originally purchased the product from a Wholesale Distributor who did not make a direct purchase from a Pharmaceutical Manufacturer, Exclusive Distributor, or Repackager.

    Tips:

    • Select the View icon on any row to view information about the Serial Number and its children.
    • Select the Export icon to export the child serial numbers aggregated to the parent Serial Number as a CSV file.