Utilisation

Pharmaceutical Manufacturers that own Uzbekistan Compliance can generate an Utilisation report to capture the serial numbers and crypto codes that are applied to the products.

Configure the report

The report for a product is generated when its product type is set to the corresponding product group in the Product Master Data:

  • Product type as Prescription Drug

  • Product type as Medical Product

The event triggers (i.e. workflow subscriptions) for the report can be set in Administer for Uzbekistan Compliance. Make sure one of the following event triggers are enabled:

Source Application Event Action Description
Serialized Operations Manager Released Generate Utilisation Report from Core Integration TraceLink generates an Utilisation report for products that are quality released when they are submitted via core integration or the Web UI, as long as all of the event trigger conditions are met.
Serialized Operations Manager Released Generate Utilisation Report from Event Exchange Integration TraceLink generates an Utilisation report for products that are quality released when they are submitted via event exchange integration, as long as all of the event trigger conditions are met.

For more information on how to enable the event triggers, see the Administer Help Center.

Uzbekistan Compliance generates the Utilisation report when TraceLink processes a Product Release or Product Release Inbound event and the following conditions are met in the interface where the event occurred:

  • The products have a Packaging Code Type of GTIN-14 with a Packaging UOM (unit of measure) of Each.
  • In Product Master Data, the serialized item is associated with an Item Code that has a Target Market as Uzbekistan.
  • In Product Master Data, Product Type is set as Prescription Drug or Medical Product.

  • The product's Pharmaceutical Manufacturer (from outside Uzbekistan), which is identified by the MAH ID for the Uzbekistan Target Market in Product Master Data, exists in Company Master Data at the company or location level.

Generate the report

To generate the Utilisation report automatically, enable the appropriate event triggers and ensure that the relevant event trigger conditions are met in Master Data Exchange. When configured, Uzbekistan Compliance generates the Utilisation report automatically when product release event occurs in one of the following interfaces:

Use any of the following Serialized Operations Manager API messages to trigger the Utilisation report:

Product Release (XML)

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

Element Values
cmn:LocationId Specify the company or location performing the product release.
tl:internalMaterialCode Specify the internal material number configured in the Product Master Data.
cbvmda:lotNumber Specify the lot number associated with the tl:internalMaterialCode.
tl:qualityControlEntityId Specify the company or location where the product is tested for quality.

Product Release Event (EPCIS v1.2)

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

Element Values
bizLocation Specify the company or location performing the product release.
tl:internalMaterialCode Specify the internal material number configured in Product Master Data.
cbvmda:lotNumber Specify the lot number associated with the tl:internalMaterialCode.
tl:qualityControlEntityId Specify the company or location where the product is tested for quality.

Use Serialized Operations Manager to trigger the Utilisation report 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 Status Update drop-down and then select Set Product Release Status.
  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:
    FieldValues
    Item CodeThe Internal Material Number or country drug code from Product Master Data.
    Lot NumberThe number associated with the packaging code.
    Quality Control EntityThe company or location where the product is tested for quality.
  5. Complete any other fields that are required in the UI or that your company uses for a specific purpose.
  6. Select Submit.

    The Set Product Release Status screen displays, and Uzbekistan Compliance begins automatically generating the report from the event trigger.

Use the Uzbekistan Compliance Web UI to manually re-generate the Utilisation report. This option is useful if a report failed to generate automatically, and the information must still be submitted to the Order Management Station (OMS).

  1. Select the Main Menu icon .

  2. Select Uzbekistan Compliance.

    A new tab opens and displays information for the Uzbekistan Compliance app.

  3. Select the Generate Report icon.
  4. Fill in the following fields:
    • Report Type drop-down – Required. Select Utilisation as the Report Type.
    • Packaging Code field – Required. The delivery number of the shipment to generate the report for.
    • Lot Number field – Required. The lot number associated with the packaging code to determine the serial numbers to report.

  5. Select Generate.

    The panel closes, and TraceLink begins generating the report. Filter to find the new report.

Report details

Field Description Sourced From OMS Report Element
Business Place ID The company identifier or location identifier as registered in government system. The company or location identifier in the Company Master Data. businessPlaceId
Report Type Displays as Utilisation. The type of report. Not reported
Status

The status of the report.

  • Generated – The report is generated in TraceLink but not yet submitted to the OMS.
  • Generation Failed – The report failed to generate in TraceLink.
  • Submitted – The report is generated and successfully submitted to the OMS.
  • Submission Failed – The report is generated but was not successfully submitted to the OMS.
  • Failed – The OMS received the report successfully but failed to provide a response.
  • Accepted – The OMS received the report successfully and accepted the information.
  • Partially Accepted – The event has multiple reports, and all of them are successfully submitted to the OMS, but the OMS did not accept all of the reports.
  • Rejected – The OMS received the report successfully but rejected the information.

The status of the report.

Not reported
Event Type

The event type:

  • Product Release
  • Product Release Inbound
 The type of event. Not reported
Date Reported The date and time that the report is generated. The system date and time when the report is generated. Not reported
Release Type Indicates whether the product is imported or locally manufactured. The manufacturing country. releaseType
Trigger Type

Indicates whether the report is generated automatically from an event trigger or manually from the Web UI.

  • System Generated – The report is generated automatically from an event trigger.
  • User Generated – The report is generated manually from the Web UI.
 Indicates whether the report is generated automatically from an event trigger or manually from the Web UI. Not reported
Product Group

The product group

  • Prescription Drug

  • Medical Product

The product group. productGroup
Field Description Sourced From OMS Report Element
Packaging Code The packaging code for the product. The Packaging Code of the serialized item in the shipment.

Not reported
Product Description The name of the product. The description associated with the Packaging Code in Product Master Data.

Not reported
Lot Number The lot number associated with the packaging code used to report the serial numbers. The lot number associated with the Packaging Code in Serialized Operations Manager for this product's serialized items. lotNumber

 
Manufacturing Country The manufacturing country for the product. The manufacturing country. manufacturerCountry
Production Date The production date for the serialized items. The production date associated with the Lot Number in Serialized Operations Manager for this product's serialized items. If the product production date does not exist in Product Master Data, the commissioning date is used. productionDate
Expiration Date The expiration date for the serialized items. The expiration date in Serialized Operations Manager for the serial numbers in this lot. expirationDate

 
Quantity The quantity of serial numbers for the Packaging Code and Lot Number. The quantity of serial numbers in the Product Release event for the Packaging Code and Lot Number. Not reported

Tips

  • Select the Export icon to export the serial numbers for a Packaging Code and Lot Number to a CSV file.

Response information when using the message status query service:

  • Report ID – The unique ID returned by the OMS for the submitted compliance report.
  • Report Name – The name of the compliance report submitted to the OMS.
  • Status – The status returned by the OMS for the submitted compliance report.
  • Status Code – The HTTPS code returned by the OMS for the submitted compliance report.
  • Description – The description returned by the OMS for the submitted compliance report.
  • Response Date – The date the response is received from the OMS.

Tips

  • Select the Action icon, and then select Export Report File to export the report file generated for the OMS.
  • Select the Action icon, and then select Export Response File to export the response file received from the OMS.