The owner-scoped trace response
3PL add-on For: Compliance manager Checked on 18.0.0.2.0, 18.0.1.0.0
What the response zip of a trace request contains once the company holds owners' stock: which units and documents are in the request's scope, and how each file of the zip is limited to it. You download the zip with Download Response on a responded request in Inventory ‣ Rx Tracking ‣ Trace Requests; the steps are in Answer trace requests while holding owner stock.
What an owner-scoped trace response contains
Every trace request of a company with owner data has a scope: the Owner Concerned, or your own records when that field is empty. Before the company's first owner profile, the response is the core response (Respond to a trace request with the response zip, and send it). Background: the add-on is built so that a response about an owner's stock holds that owner's records only, and so that a response about units you bought from an owner in place holds the transfer and the owner's upstream hop (FD&C Act § 582, requests for information; see Compliance background).
What is in the scope
| Record | In the scope of an owner's request | In the scope of a request about our own records |
|---|---|---|
| Units (the Packages tab) | units held for the owner, sold by it, or moved while they were held for it; a unit on an open receipt belongs to that receipt's owner | your units, units you sold, and units moved while they were yours |
| Documents (the Documents tab) | documents issued in the owner's name or received for it (DSCSA/CODE/…) | your own documents (DSCSA/OUT/…, DSCSA/IN/…), including the inbound document of a unit you bought from an owner in place |
| Left out | your units and other owners' units; the chatter note "Left out by this request's owner scope …" counts them | every owner's units and documents; the same note names the owners |
A unit can be in two scopes, for different periods: a unit you bought from an owner in place is in the owner's scope for the time it was held for the owner, and in yours from the transfer on. Each response shows only its own period of that unit.
The files of the zip
| File | In an owner-scoped response |
|---|---|
request.txt | the core text, plus two lines under "Company: …" on an owner's request: "Prepared by COMPANY as third-party logistics provider on behalf of OWNER" and "Owner's approval: WHO, reference REFERENCE, on YYYY-MM-DD". A request about your own records has the core text only |
index.csv | one row per product line of each document in the scope, with the SHA-256 of its files |
documents/NUMBER/ | the files frozen with each document in the scope: the T3 report and EPCIS file of an owner's outbound document, the supplier's file of an owner's inbound document |
packages.csv | only the package-ledger rows of the scope's movements. The owner column (last) names the owner on an owner's rows and is empty on yours; the dscsa_document column names only the scope's documents of that movement |
The columns of packages.csv are date_utc, movement, reference, dscsa_document, source_location, destination_location,
partner, partner_gln, product, ndc, gtin14, serial, sgtin, lot, expiry_date, sscc, package_state and owner.
Examples from the example database
Northwind Generics LLC's request about lot BPDPZ2508K (12 of Northwind's units, 24 of yours and 12 of Summit's in the lot): the response
holds Northwind's two documents and 12 units. Its packages.csv has, for example, these rows for unit 600000011001 (shipped to
Riverside, then returned):
| movement | reference | dscsa_document | package_state | owner |
|---|---|---|---|---|
receipt | WH/IN/00007 | DSCSA/NWG/IN/2026/00001 | returned | Northwind Generics LLC |
shipment | WH/OUT/00012 | DSCSA/NWG/OUT/2026/00001 | returned | Northwind Generics LLC |
customer_return | WH/IN/00017 | (empty) | returned | Northwind Generics LLC |
Unit 600000023001 of Prototamol lot BPPTM2509A, received for Summit Specialty Pharma Inc. and then bought by you in place (title
transfer WH/TT/00001):
| Response | Rows of that unit in packages.csv | Documents in the zip |
|---|---|---|
| Summit's request (Owner Concerned Summit) | receipt (WH/IN/00018, DSCSA/SSP/IN/2026/00002) and title_out (WH/TT/00001, DSCSA/SSP/OUT/2026/00002), owner Summit Specialty Pharma Inc. | Summit's inbound document and its side of the title transfer (T3 and EPCIS) |
| Your request (Owner Concerned empty) | title_in (WH/TT/00002, DSCSA/IN/2026/00001), owner empty | your in-place inbound document, with the copy of Summit's EPCIS file it stores |
Record numbers are those of a freshly built example database; yours differ.
What doesn't change
- The due date is the core's 24-hour internal target from Received On; the software keeps no per-owner response time.
- Responding closes the request as in core: the approval fields, Owner Concerned and the query can't be changed afterwards.
- The zip is stored with the request and in its chatter, with its SHA-256, as for your own requests.
Related procedures: Answer a trace request about an owner's records, Answer a trace request about our own records while we hold owners' stock.