Troubleshooting
Every error or warning a user can meet has an entry: what you see, when, the cause, the remedy and who can fix it. Type a distinctive part of the message into the search box at the top of the page (Ctrl+K, or ⌘K on a Mac), or open the page of the task you were doing. Abbreviations in the titles, such as EPCIS (Electronic Product Code Information Services), are explained in the Glossary.
Messages every guide can show
These have one shared entry each, on Access, companies and setup:
- Error: "Only DSCSA users can ..."
- Error: "Only a DSCSA manager can ..."
- Error: "You are not allowed to access ... records"
- Error: "Uh-oh! Looks like you have stumbled upon some top-secret records"
- Error: "... belongs to another company"
- Error: "... can't be changed" or "... can't be deleted" on a kept record
- Error: "... not an authorized trading partner" when you have no Rx Tracking right
- Error: "Third-party logistics (3PL) is off for ..."
- Error: "DSCSA owner isolation (3PL): ..."
- Error: "DSCSA products can't be consumed or produced here ..."
- A non-DSCSA product is refused
- The Rx Tracking modules aren't in Apps
- There is no Sales app after installing Rx Tracking
- An Enterprise add-on won't install
- After an update, Apps still shows the old version
- A user has no Rx Tracking menu
- An email or a reminder never arrived
- A scheduled job didn't run
Core
- Configuration
- Products, partners and licenses
- Receiving
- Supplier files, statements and discrepancies
- Selling and shipping
- Returns and the customer portal
- Quarantine, scrap and trace requests
- Opening balance, counts and records
- Off-site archive and scheduled jobs
3PL
- 3PL setup
- Owner profiles and instructions
- Owner receipts and owner isolation
- Goods before data
- Owner shipments
- Owner documents and trace requests
- Owner notices, holds and recalls
- Owner returns and adjustments
- Title transfers
- Just in time and consignment
- Facility compliance records and the owner checks
- Owner reports and exports
- The owner portal
Enterprise add-ons
Every entry
All 482 entries, page by page, in the order of the pages above. Each page lists its most frequent entries first. Messages every guide can show are listed once, under the first page.
Troubleshooting: access, companies and setup
Troubleshooting: access, companies and setup: 18 entries.
- Error: "Only DSCSA users can ..."
- Error: "Only a DSCSA manager can ..."
- Error: "You are not allowed to access ... records"
- Error: "Uh-oh! Looks like you have stumbled upon some top-secret records"
- Error: "... belongs to another company"
- Error: "... can't be changed" or "... can't be deleted" on a kept record
- Error: "... not an authorized trading partner" when you have no Rx Tracking right
- Error: "Third-party logistics (3PL) is off for ..."
- Error: "DSCSA owner isolation (3PL): ..."
- Error: "DSCSA products can't be consumed or produced here ..."
- A non-DSCSA product is refused
- The Rx Tracking modules aren't in Apps
- There is no Sales app after installing Rx Tracking
- A user has no Rx Tracking menu
- After an update, Apps still shows the old version
- An Enterprise add-on won't install
- An email or a reminder never arrived
- A scheduled job didn't run
Troubleshooting: configuration
Troubleshooting: configuration: 7 entries.
- The DSCSA (Rx Tracking) block isn't in the settings
- Error: "You are not allowed to access 'Config Settings'"
- Error: "GLN '…' has an invalid check digit"
- Error: "The GS1 company prefix length must be between 6 and 12"
- The delivery email has no DSCSA files
- Error: "The contact "…" does not have a valid email"
- Documents show an empty Transaction Statement or have no EPCIS file
Troubleshooting: products, partners and licenses
Troubleshooting: products, partners and licenses: 24 entries.
- Error: "… can't be confirmed: it contains DSCSA products …"
- Error: "… has no valid state license: license … expired on …"
- Error: "… has no valid state license: license … is unverified."
- Error: "… has no valid state license: none on file."
- Error: "… has no DSCSA role set, so it is not an authorized trading partner."
- Error: "… license … is not in force until …"
- Error: "… has no valid FDA 503(e) annual report: …"
- Error: "Delivery address …: …"
- Error: "… but no trading partner is set on the transfer."
- Warning: "The DSCSA document of this shipment will have no EPCIS file …"
- Error: "NDC '…' has 10 digits but no hyphens …"
- Error: "GTIN '…' has an invalid check digit …"
- Error: "The GTIN … of … is already used by …"
- Error: "… is a DSCSA product and must be tracked by lots …"
- Error: "These products are in the DSCSA record and must stay DSCSA products …"
- Error: "The GS1 company prefix length … must be between 6 and 12 …"
- Error: "GLN '…' has an invalid check digit …"
- Error: "… is flagged as a small business dispenser …"
- Error: "Enter where … was verified …"
- Error: "License … cannot expire before it is issued."
- Error: "Record license … on the company …, not on its contact or address …"
- Error: "… is verified: the verification is evidence for its …, which can't change."
- Error: "… cannot be deleted: verified licenses are verification evidence …"
- No license-expiry reminder arrives
Troubleshooting: receiving
Troubleshooting: receiving: 22 entries.
- Error: "… can't be validated: scan one DSCSA serial for each unit being validated"
- Error: "You need to supply a Lot/Serial number for products …"
- Error: "Some lines could not be read"
- Error: "… the scan has no lot number (AI 10)" or "a package scan needs a GTIN (01) and a serial number (21)"
- Error: "… is not on this transfer" or "… is not a DSCSA product"
- Error: "no DSCSA product has GTIN …"
- Error: "SSCC … is not a case the supplier's EPCIS file lists for this transfer"
- Error: "… is already scanned on …"
- Error: "Serial … belongs to …"
- Error: "… is already registered (state: …). A duplicate serial is a suspect-product signal"
- Error: "the scan says lot … expires …, but the lot expires …"
- Error: "Scan or paste at least one package DataMatrix."
- Error: "… is already done or cancelled."
- Error: "The buyer in the file has GLN …" or "The seller in the file has GLN …"
- Error: "GTIN … is not on any product"
- Error: "… is in the file but not on …"
- Error: "These serials are already expected on another open receipt"
- Error: "… can't be read as an EPCIS 1.2 file"
- Error: "The file announces no serialized packages" or "… package(s) have no lot number in the file"
- Error: "… has no open receipt to import a supplier EPCIS file on"
- Error: "DSCSA packages don't match the quantities being validated"
- The Scan Serials or Import EPCIS button isn't shown
Troubleshooting: supplier files, statements and discrepancies
Troubleshooting: supplier files, statements and discrepancies: 23 entries.
- Error: "Confirm that the supplier's statement affirms the §581(27) Transaction Statement …"
- Error: "Attach the evidence file(s) …"
- Error: "Upload the evidence files in the Record Transaction Statement window …"
- Error: "The date the Transaction Statement was obtained can't be in the future."
- Error: "Invalid fields: Where Was It Obtained?"
- Error: "Supplier file … is no longer awaiting its receipt …"
- Error: "Choose the discrepancies or the supplier file to record the Transaction Statement for."
- The lot stays quarantined
- Error: "Write how the discrepancy was resolved first …"
- Error: "Only a DSCSA manager can reopen a discrepancy."
- A supplier file, a discrepancy or its receipt can't be deleted or changed
- Error: "Only an import awaiting its receipt can be cancelled …"
- Error: "… this done DSCSA operation can't be edited …"
- Every unit of the file is a duplicate, and the receipt won't validate
- A discrepancy is past its deadline
- Error: "Which holds keep a lot quarantined is recorded by the system."
- Warnings on a supplier file's Warnings tab
- Warning: "The seller has not affirmed the DSCSA Transaction Statement in this file …"
- Warning: "… the file announces N package(s) but the receipt expects M."
- Warning: "… has no GLN in Odoo, so the … in the file (GLN …) could not be checked."
- Warning: "N shipped package(s) have no expiry date …"
- Warning: "Products that are not DSCSA products were left out …"
- Warning: "The file has no shipping event …" and other file-format notes
Troubleshooting: selling and shipping
Troubleshooting: selling and shipping: 16 entries.
- Error: "Serial … can't be used here: it is …"
- Error: "… packages scanned but only … ordered."
- Error: "Serial … is not in the package ledger …"
- Error: "the scan says lot … but the ledger has lot …"
- Error: "… only … more unit(s) of lot … are available in …"
- Error: "SSCC … is not a case the supplier's EPCIS file lists for this transfer" on a delivery
- A small dispenser's delivery asks for serial numbers
- Warning: "No EPCIS file was generated: …"
- Error: "This order can't be paid online yet."
- The customer's Accept & Sign button keeps spinning
- The DSCSA Documents smart button isn't shown
- Send message is greyed out on a DSCSA document
- Error: "The T3 report of DSCSA document … was frozen when it was posted …"
- Error: "DSCSA document … has no stored T3 report."
- Error: "The DSCSA hash chain of … is broken …"
- Error: "The T3 report of DSCSA document … could not be rendered as a PDF."
Troubleshooting: returns and the customer portal
Troubleshooting: returns and the customer portal: 16 entries.
- Error: "Serial … was shipped to …, not to …"
- Error: "… was never shipped …" or "… is not in our package ledger …"
- Error: "Serial … can't be used here: it is …"
- Error: "The return can't be created: …"
- Error: "… matched at lot level …" or "no unit of lot … shipped to … without serials is still out"
- Error: "…: set the customer on the return first"
- Error: "… can't be validated: these returned serials don't match our own sales"
- Error: "Returned DSCSA units in … are waiting for verification."
- Verify for Resale and Reject and Destroy aren't shown
- Error: "Only returned packages that are not on an open transfer can be verified or rejected"
- Error: "… its stock location is unknown …", "… has no scrap location." and similar
- The Non-saleable return checkbox isn't shown
- Error: "The non-saleable return flag of … can't change"
- A customer's document link shows "Error 404", "Not Found" or the sign-in page
- A customer doesn't see a document, or the DSCSA Documents card, in the portal
- The order page says "sign in to download them"
Troubleshooting: quarantine, scrap and trace requests
Troubleshooting: quarantine, scrap and trace requests: 25 entries.
- Error: "These lots are quarantined and can't be shipped …"
- Error: "Serial … can't be used here" on a scrap
- Error: "… serial(s) scanned for … scrapped"
- Error: "Invalid fields: Lot/Serial" on a scrap
- Error: "Serial … is in lot …, not in the scrapped lot …"
- Error: "Serial … is in …, not at …"
- Error: "… is a DSCSA product: scan the serial of each unit being scrapped"
- Error: "a case (SSCC) label can't be used here"
- Error: "Only DSCSA users can scrap …"
- Error: "… can't be added to …: it is done" when scrapping from a transfer
- Error: "DSCSA stock (…) can only be relocated …"
- The Quarantine or Release button isn't shown
- Error: "Give a reason for the quarantine."
- Error: "These lots are not quarantined."
- Errors when quarantine fields are imported or set through the API
- Error: "Enter at least one serial, lot, product, GTIN or transaction date."
- Error: "Some serial lines could not be read"
- Error: "The transaction date range of … ends before it starts."
- Warning: "Not found: …" on a trace request
- Error: "The stored files of these DSCSA documents don't match their checksums"
- Error: "Search trace request … before responding."
- Error: "Only DSCSA managers can do this on a trace request."
- The trace request reminder went to the wrong person or date
- Errors when trace requests are imported or changed through the API
- Error: "The serials of a done scrap are recorded in the package ledger and can't be changed."
Troubleshooting: opening balance, counts and records
Troubleshooting: opening balance, counts and records: 25 entries.
- Error: "… serial(s) scanned, but only … unit(s) … have no package yet"
- Error: "Nothing was registered. Fix these scans and try again"
- Error: "Serial … is already in the package ledger"
- Error: "Choose the lot, or scan packages of one lot (AI 10)."
- Error: "Scan or paste at least one package DataMatrix."
- Error: "Only DSCSA managers can register an opening balance in the package ledger."
- The Ledger vs Stock report lists a lot
- Error: "… unit(s) counted as gone. Name their serials"
- Error: "… serial(s) named for … unit(s)"
- Error: "Serial … is in lot …, not in lot …" in a count
- Error: "Only DSCSA users can apply a count that lowers the stock …"
- Error: "Only DSCSA managers can apply a count that raises the stock …"
- Error: "… a count can only find a package recorded as missing."
- Error: "… DSCSA stock is tracked by lot. Count it on a line with its lot."
- Error: "Inventory adjustments of DSCSA products can't be reverted"
- The Packages list finds no package for a serial
- Error: "DSCSA packages change only through the package ledger's own operations"
- Error: "These lots appear in posted DSCSA documents …"
- Error: "Give the reason for placing or releasing the legal hold."
- Error: "Only DSCSA managers can place or release a legal hold."
- A second legal hold isn't recorded
- Error: "Only DSCSA managers can export the package ledger and license register."
- Verify Integrity reports a problem
- Error: "The DSCSA hash chain of … is broken"
- Error: "These files are DSCSA records that must be kept …"
Troubleshooting: off-site archive and scheduled jobs
Troubleshooting: off-site archive and scheduled jobs: 24 entries.
- Last Error: "No reply from S3 (…)"
- Last Error: "The S3 archive settings of … are incomplete: …"
- Last Error: "HTTP 403 Forbidden: SignatureDoesNotMatch …" or another "HTTP …" error
- Last Error: "S3 already holds an object under this key, and this job never stored one …"
- Last Error: "The content of … no longer matches the SHA-256 recorded when it was queued …"
- Last Error: "Unexpected error: …" or "The access key ID contains characters that are not allowed."
- Archive jobs stay Pending
- Error: "Oops! Something went wrong" on Queue Unarchived Records
- Error: "Enable the off-site S3 archive in the Inventory settings first."
- Error: "Only failed or pending archive jobs can be retried."
- Error: "Only DSCSA managers can manage the S3 archive queue."
- Error: "S3 archive jobs are queued only by the archive itself." and related refusals
- Error: "Invalid fields: S3 Bucket, S3 Access Key ID"
- Error: "Invalid S3 bucket name …"
- Error: "The region may only contain lower-case letters, digits and "-" …"
- Errors about the endpoint URL
- Error: "The S3 key prefix may only contain letters, digits …"
- Error: "The S3 archive retention must be between 6 years (the DSCSA minimum) and 30 years."
- Error: "The S3 archive test retention must be between 1 and 30 days."
- The archive settings aren't shown
- Error: "Only DSCSA managers with access to the Settings can set the S3 archive secret key."
- A copy of the database still has the archive on
- Error: "Oops! Something went wrong" when the license reminder job runs
- A reminder went to the wrong person, or to nobody
Troubleshooting: 3PL setup
Troubleshooting: 3PL setup: 17 entries.
- The 3PL settings block is missing
- Error: "3PL can't be turned on for … DSCSA stock is already held for …"
- Error: "3PL can't be turned off for … while owner profiles are active …"
- Error: "3PL can't be turned off for …: DSCSA stock is still held for …"
- Error: "Consignor owners can't be turned off while …"
- Error: "This document-issuance setting would put … in issuing mode A …"
- Error: "Only DSCSA managers can change the third-party logistics (3PL) settings."
- Error: "The 3PL owner-data flag and the title-transfer location are set by the system."
- Held for Owner doesn't show although 3PL is on
- 3PL fields show on transfers while 3PL is off
- Error: "Licence … names the facility …, which belongs to …"
- Error: "… is verified: the verification is evidence for its …"
- A facility license is missing from Facility Licences, or doesn't count
- Error: "Enter where the rule of … was verified …"
- Error: "… already has a jurisdiction record in …"
- Error: "The jurisdiction record of … is verified …"
- Error: "A jurisdiction is verified with the "Mark verified" button …"
Troubleshooting: owner profiles and instructions
Troubleshooting: owner profiles and instructions: 28 entries.
- Error: "OWNER's instruction (KIND) is required for …"
- Error: "Instruction … is not a … instruction."
- Error: "Instruction … is from …, not from …"
- Error: "Instruction … was already used on …"
- Error: "Instruction … belongs to another company."
- Error: "… has no active owner profile in …: instructions are recorded for owners only."
- Error: "Owner instructions are frozen once recorded …"
- Error: "Owner code … use 2 to 12 capitals …"
- Error: "Another owner of this company already uses this document code."
- Error: "This partner already has an owner profile in this company (it may be archived)."
- Error: "The company's own stock needs no owner profile."
- Error: "The service end date is before its start date."
- Error: "The TI business address of … must be the owner or one of its addresses."
- Error: "Turn on third-party logistics …"
- Error: "Record the reference of … written authorization …"
- Error: "Only DSCSA managers record an owner's authorization …"
- Error: "Just-in-time transfers for … need issuing mode B …"
- Error: "Consignor owners are turned off …"
- Error: "An owner profile's owner and company can't change …"
- Error: "Owner profiles are never deleted …"
- Error: "… has no active owner profile, so DSCSA stock can't be held for it …"
- The owner is not an authorized trading partner
- Error: "The contact … does not have a valid email."
- Error: "The owner profile of … is archived …"
- Error: "… is not a contact of …"
- Error: "… is an internal user …"
- Error: "… already has the owner portal of …"
- Error: "Only DSCSA managers grant or revoke the owner portal."
Troubleshooting: owner receipts and owner isolation
Troubleshooting: owner receipts and owner isolation: 24 entries.
- Error: "DSCSA owner isolation (3PL): …"
- Error: "… is held for …, not for …: it can't be used on this transfer."
- Error: "… was announced by the supplier for …'s receipt …: receive it there."
- Error: "…: hold DSCSA stock for the owner company …, not for its contact …"
- Error: "…: … has no active owner profile, so DSCSA stock can't be held for it (Rx Tracking > 3PL)."
- Error: "… is on our sale or purchase order: its DSCSA units can't be held for …"
- Error: "…: unreserve the transfer (or undo its scans) before changing the owner its units are held for."
- Error: "… mixes DSCSA stock of several owners (…): one transfer per owner."
- Error: "… is done: the owner its DSCSA units were held for can't be changed."
- Error: "Package … would hold units of several owners (…): unpack it first, one package per owner."
- Error: "The buyer in the file has GLN …, but … has …"
- Error: "The file ships the goods to location GLN …, which is not one of our GLNs …"
- Error: "… is a custody receipt (…), but the file names another seller …"
- Error: other refused supplier files on an owner receipt
- Find Receipt proposes the wrong receipt, or none
- Error: "…'s profile releases goods received before their data only with the supplier's data …"
- Error: "The date of the owner's confirmation can't be in the future." and other input checks
- Error: "The supplier's data is already recorded for …"
- Error: "… (custody receipt): …'s instruction (…) is required for …"
- Error: "Only a DSCSA manager can record a receipt as custody …"
- Error: "… is done: whether it was the owner's purchase or a custody receipt can't be changed any more."
- Error: "Only DSCSA users can record the supplier's data or the owner's confirmation."
- The yellow banner or the Attach Supplier Data button isn't shown
- An internal transfer doesn't take the owner's units
Troubleshooting: goods before data
Troubleshooting: goods before data: 11 entries.
- The owner's units can't be shipped after the receipt
- The lot stays quarantined after the data is recorded
- Error: "Validation Error … Owner Release Instruction (Release Window) … Field: Lot (lot_id)"
- Error: "A supplier file is already recorded for …"
- Error: "None of the packages the file lists was received on …"
- The Supplier Data Pending item was closed without data
- Warning: "… They become discrepancies when the receipt is validated." on a late file
- The owner's upload was refused
- Error: "Choose open 'Supplier data pending' discrepancies …"
- Errors met only through imports and API calls
- Other refusals of a late file
Troubleshooting: owner shipments
Troubleshooting: owner shipments: 12 entries.
- Error: "… can't be confirmed: it ships DSCSA products for …"
- Error: "… can't be confirmed:" (the order itself)
- Error: "… ships lot … of … only."
- Error: "… is not on …" or another line that doesn't match the order
- Error: "… can't buy its own goods …", "A custody return goes to …" and the other order rules
- Error: "… has shipped transfers …" or "… was confirmed: it is kept …"
- Error: "… is confirmed: its owner, parties, lines and instruction can't change …"
- Error: "… a custody shipment goes to … or one of its addresses, not to …"
- Error: "… the procurement would buy …" or "… the procurement created no transfer."
- Warning: "DSCSA warning: the owner's document of this shipment will have no EPCIS file …"
- The owner's delivery stays Waiting
- Held for Owner doesn't show on a new delivery
Troubleshooting: owner documents and trace requests
Troubleshooting: owner documents and trace requests: 19 entries.
- Error: "… has not authorized us to send its documents to its customers …"
- The Publish to Buyer window shows a red banner
- Send Documents to Owner or Publish to Buyer isn't shown
- Error: "Not owner documents (ours go to our customers): …"
- Error: "Send the documents of one owner at a time."
- Error: "Choose the owner's contacts to send the documents to."
- The owner didn't get its documents by email
- Warning: "No EPCIS file was generated: the owner … has no GLN"
- The buyer opened a mode-A owner document from an email link
- Error: "The buyer's access to … changes only through "Publish to Buyer" …"
- Other messages of Send Documents to Owner and Publish to Buyer
- Error: "Trace request … concerns the records we hold for …: … needs its approval"
- Error: "… is not an owner of …: a trace request concerns our own records …"
- Error: "The owner's approval of trace request … can't be dated in the future."
- Error: "Trace request … concerns our own records: there is no owner approval to record."
- The results and the owner's approval disappeared after changing Owner Concerned
- A unit we hold is "Not found", or the chatter says units were "Left out by this request's owner scope"
- Owner Concerned isn't shown on the trace request
- Error: "The package ledger rows of trace request … can't be matched to their movements …"
Troubleshooting: owner notices, holds and recalls
Troubleshooting: owner notices, holds and recalls: 17 entries.
- Error: "The release needs each owner's instruction (the owner directs the release of its stock): …"
- Error: "Invalid fields: Reference"
- Error: "Give a reason for the release."
- The owner says it got no notice
- Error: "… still no notice contact with an email address in the owner profile."
- Error: "These notices were already sent."
- Error: "These owners' units are on an owner hold and can't be shipped …"
- An owner hold stays active after its discrepancies are resolved
- The owner's units stay Quarantined after a release
- The Owner Holds list is empty
- Error: "This owner hold is already released."
- Error: "Only a DSCSA manager can quarantine or release a lot." on a recall
- Error: "… has no 3PL owners." or "… is not a 3PL owner of …"
- Error: "You are not allowed to access … (3PL) records"
- Error: "The related record no longer exists."
- Error: "Owner notices are created by the operations they report …"
- Error: "Owner holds are placed by the receiving flows of owner receipts, not by hand."
Troubleshooting: owner returns and adjustments
Troubleshooting: owner returns and adjustments: 13 entries.
- Error: "Serial … was sold by …: it can only come back into …"
- Error: "Returned units held for an owner are destroyed only on the owner's instruction"
- Error: "… a nonsaleable return of units held for … goes to … or to one of its return designees …"
- Error: "… a custody return gives units back to …, so it goes to … or one of its addresses …"
- Error: "Lot …: … serial(s) matched at lot level …, but only … unit(s) … are still out."
- Held for Owner is missing on a new delivery
- Error: "Serial … is held for …, not for …: count it on that owner's line."
- Error: "… count DSCSA stock held for the owner company …" or "… is not an owner of …"
- Error: "… can't be scrapped: the serials are held for several owners …"
- Error: "The serials are held for …, but the scrap is for …"
- Error: "… serial(s) scanned, but only … unit(s) … have no package yet" for an owner
- Error: "… has no active owner profile, so DSCSA stock can't be registered as held for it"
- Error: "The owner instruction of a done scrap is part of its record and can't be changed."
Troubleshooting: title transfers
Troubleshooting: title transfers: 30 entries.
- Error: "The title transfer can't be validated: …"
- Error: "Title transfers are not allowed for …"
- Error: "… has no active owner profile: we only buy in place from our owners."
- Error: "… it has no DSCSA product …" or "… one line per DSCSA product."
- Error: "These serials can't be selected …"
- Error: "… only units in stock and sellable change owner."
- Error: "… is scanned on …: take it off that transfer first."
- Error: "Nothing was selected. Fix these scans and try again: …"
- Error: "Lot …: only N unit(s) held for … are in stock in … and free."
- Error: "… selected but only … left to receive …"
- Error: "Lot … is picked on …: unreserve that transfer first."
- Error: "Package … also holds units that don't change owner …"
- Error: "Seller: …" or "Buyer: …"
- Error: "Facility … has no valid … licence"
- Error: "… transaction information and statement must be on file …"
- Error: "… does not affirm the Transaction Statement …"
- Error: "… instruction (Title transfer) is required …"
- Warning: "Case … is split …"
- No Validate button, or "Only a DSCSA manager can validate a title transfer."
- Error: "The seller in the file has GLN …" on a title transfer
- Error: "None of the … serial(s) the file lists can change owner …"
- Error: "… can't be read as an EPCIS 1.2 file"
- The transfer's setup is refused
- Error: "An owner-to-owner transfer needs two different owners."
- Error: "Unable to cancel purchase order(s) …" or "You cannot decrease the ordered quantity …"
- A buyer can't cancel a confirmed purchase order: "Access Error … DSCSA Package"
- Customer Invoice shows an Access Error
- Error: "… is a title-transfer picking: only its title transfer validates it …"
- Error: "… has no Title Transfer operation type …"
- Error: "Third-party logistics (3PL) is off …" on a purchase order
Troubleshooting: just in time and consignment
Troubleshooting: just in time and consignment: 9 entries.
- Error: "… package(s) held for … scanned but … of its unit(s) picked."
- Error: "TT/… can't be validated:" when you validate a delivery
- Error: "… is held for …, not for …: it can't be used on this transfer."
- Error: "… takes units held for …, but the move is for our own stock."
- The owner's units are never taken by our sales
- The in-place documents have no EPCIS file
- Error: "…: only … more unit(s) of lot … held for … are available in …"
- Error: "Lot …: … holds … unit(s) of … there, not …"
- Error: "… is a consignor, and consignor owners are turned off in the 3PL settings."
Troubleshooting: facility compliance records and the owner checks
Troubleshooting: facility compliance records and the owner checks: 22 entries.
- Error: "… can't be validated: it moves DSCSA products … to or from a trading partner."
- Error: "… (ROLE) has no valid …" (the other party)
- Error: "Owner: … has no valid …"
- Error: "Facility … has no valid 3PL licence …"
- Error: "… does not license 3PLs, so the report stands in for the state licence."
- Error: "… which the company's 503(e) setting requires."
- Error: "… but no trading partner is set on the transfer."
- Error: "… is not at one of our facilities, so our licence for it can't be checked."
- Warning: "Trading-partner check for owner … let through with a warning"
- Error: "Enter the submission date and FDA's confirmation of … before marking it submitted."
- Error: "Enter the reporting year of the FDA annual report (e.g. 2026)."
- Error: "Only DSCSA managers can mark …"
- Error: "… is already submitted." or "… is already reported."
- Error: "… is submitted: its … can't change. Archive it and record a new report."
- Error: "Enter the date the FDA report was updated and FDA's confirmation for … before marking it reported."
- Error: "… is not a licence of the facility …"
- Error: "… is reported: its … can't change. Archive it and record a new event."
- There is no FDA annual report reminder
- The FDA annual report reminder is overdue the day it appears
- Error: "… no longer exists (its operation was refused and rolled back)."
- Error: "The gate log is a record of checks made …"
- The facility client list misses an owner, or lists one it shouldn't
Troubleshooting: owner reports and exports
Troubleshooting: owner reports and exports: 10 entries.
- An owner report is empty or leaves an owner out
- Our On Hand is lower than the units on the shelf
- The owner reports aren't in the menu, or an Access Error opens
- Ledger vs Stock per Owner lists a lot
- Error: "Only DSCSA managers can export an owner's records."
- Error: "… is not an owner of …"
- Error: "The export period ends before it starts."
- Error: "The stored files of these DSCSA documents don't match their checksums …"
- Errors an import or integration gets on owner exports
- A draft owner export made by mistake can't be deleted
Troubleshooting: the owner portal
Troubleshooting: the owner portal: 17 entries.
- The owner sees no owner card on My account
- Error: "… was not imported:" after the owner's upload
- Error: "… some serial numbers it lists are already expected on another receipt …"
- Error: "… was not received: 10 files were already uploaded to … in the last 24 hours …"
- Error: "… can't be uploaded: only the supplier's EPCIS file (.xml) or its transaction statement as a PDF (.pdf) are accepted."
- Error: "… is too large: files up to 10 MB can be uploaded." or "Request Entity Too Large"
- Error: "Choose the supplier's file to upload."
- The owner gets "Error 404" on an owner page
- The owner can't see a subsidiary's stock or documents
- The owner's upload ends on "Error 404"
- The owner's upload ends on "Oops! Something went wrong."
- A receipt the owner expects isn't on its Receipts page
- The owner uploaded a PDF, but the receipt is still pending
- A "Received for you" document has no file on the owner portal
- A document the owner expects isn't on its Documents page
- The owner can't read, or asks about, the reason of a hold
- The owner's stock on the portal differs from your Owner Stock report
Troubleshooting: the Barcode app
Troubleshooting: the Barcode app: 22 entries.
- The Barcode app says "This product doesn't exist."
- Error: "Only DSCSA users can scan DSCSA serials onto a transfer"
- Warning: "Serial … is already scanned on this transfer"
- Error: "… can't be used here: it is …"
- Error: "… is not in the package ledger, so it can't be shipped or moved"
- Error: "… is already registered (state: …). A duplicate serial is a suspect-product signal …"
- Error: the scan's lot or expiry doesn't match
- Error: "… is not on this transfer"
- Error: "… packages scanned but only … ordered"
- Error: "This barcode can't be read as a GS1 DataMatrix"
- Error: "… is held for …, not for …" (3PL)
- Error: "… was announced by the supplier for …'s receipt …: receive it there" (3PL)
- Error: a returned unit doesn't match our sale
- Error: "… was sold by …: it can only come back into the stock of …" (3PL)
- Other scan refusals
- The transfer won't validate from the Barcode app
- Error: "The inventory adjustment can't be applied"
- Error: scrap refused in the Barcode app
- A sealed case's label records nothing
- A lot is quarantined after validating a receipt in the app
- The line shows a wrong count, or no backorder question
- A product left at 0 was shipped anyway
Troubleshooting: suspect-product investigations
Troubleshooting: suspect-product investigations: 17 entries.
- A quarantine opened no investigation
- The Quarantine Lot or Release Lot button isn't shown
- The Lot list offers only "Create"
- The DSCSA fields and tabs aren't shown
- The investigation stays open after the lot is released
- Form FDA 3911 items are empty, or show another lot
- Error: "Only lots of DSCSA products can be quarantined"
- Error: "Lot … is already quarantined."
- Error: "No quality team found for this company."
- Errors when investigations are changed through an import or the API
- Error: "… is not an owner (3PL client) of …: it has no owner profile."
- Error: "… leave the investigated owner empty for our own stock."
- Error: "… only a DSCSA investigation has an investigated owner."
- Error: "… FDA was notified for this investigation, so its investigated owner can't change."
- Error: "Every owner holding units of lot … already has an open investigation of it."
- Error: "… is closed." when you split
- Errors when an investigation is split through the API
Troubleshooting: illegitimate product and Form FDA 3911
Troubleshooting: illegitimate product and Form FDA 3911: 14 entries.
- The banner stays after FDA was recorded as notified
- Error: "… is before the determination date."
- Error: "… the determination date can't be in the future."
- Error: "Invalid fields: Determined Illegitimate On"
- Error: "… a termination can only be requested after FDA was notified."
- Error: "… FDA can only approve a termination on or after the day it was requested."
- A closed investigation is still overdue
- Find Trading Partners adds nobody, or isn't shown
- No deadline, banner or activity on an illegitimate product
- Items are blank on the Form FDA 3911 data sheet
- Type of Report is wrong, or item 19 isn't shown
- The deadline activity names another deadline
- The deadline counted as met although no trading partner was notified
- Nobody is reminded of an unanswered termination request