Troubleshooting: goods before data
3PL add-on For: Warehouse staff, Compliance manager Checked on 18.0.0.2.0, 18.0.1.0.0
What to do when an owner's goods received before their supplier data stay held, when a late supplier file is refused or finds differences, or when an owner's portal upload doesn't reach the receipt. Entries are ordered from the most frequent.
The refusals shared with open owner receipts (the file's buyer, ship-to or custody seller, Find Receipt, the owner's confirmation and its fields, "already recorded", the rights) are on Troubleshooting: owner receipts and owner isolation. The statement document's field errors are on Troubleshooting: receiving discrepancies.
The owner's units can't be shipped after the receipt
What you see: the receipt held for an owner is Done with the red banner "Supplier data pending: this owner's goods were received before the supplier's transaction information and statement, so their DSCSA lots are held. …". An owner delivery of these units reserves nothing, and the lot shows Quarantined. Your own sales of the same lot may lose their reservation too.
When: after Validate in Receive an owner's goods before their data.
Cause: the receipt was received (Validate) without the supplier's EPCIS file, its statement document or the owner's confirmation, so its DSCSA lots are held under a Supplier Data Pending discrepancy. With the default Hold scope (Whole lot) the hold covers every unit of the lot: yours and every owner's.
Remedy: resolution. Record whichever arrives first:
- the supplier's late EPCIS file: Release a data-pending hold with the supplier's late EPCIS file;
- the supplier's statement document: Release a data-pending hold with the supplier's transaction statement document;
- the owner's confirmation: Release a data-pending hold with the owner's confirmation.
Next time, record the data or the confirmation before you validate (Record the owner's confirmation or the supplier's statement before validating).
Who can fix it: Rx Tracking User or Manager.
The lot stays quarantined after the data is recorded
What you see: the red banner is gone and the Supplier Data Pending discrepancy is Resolved, but the lot is still Quarantined. The lot's chatter says:
The Transaction Statement for DISC/YYYY/NNNNN was recorded, but lot LOT stays quarantined: still held by open discrepancy DISC/YYYY/NNNNN TYPE SERIAL; ... Release the lot once nothing else holds it.
When: after 3PL-GBD-02, 3PL-GBD-03 or 3PL-GBD-04.
Cause: something else holds the lot: the differences the late file found (Missing, Extra, Wrong Lot, Wrong Expiry, Duplicate Serial), a Transaction Statement Missing discrepancy (the late file doesn't affirm the statement), another receipt's discrepancy, or a manager's own quarantine. The data releases only what nothing else holds.
Remedy: resolution.
- Read the lot's Quarantine tab and chatter: they list every reason.
- For the late file's differences, see Resolve the differences a late supplier file finds.
- For a Transaction Statement Missing discrepancy, see Record a missing Transaction Statement after validation and release the lots.
- For a manager's quarantine, see Release a lot that holds owner units, with each owner's release instruction (and the Known issue in Error: "Validation Error … Owner Release Instruction (Release Window) …").
Who can fix it: Rx Tracking User or Manager for the discrepancies; Rx Tracking Manager for the lot's release.
Error: "Validation Error … Owner Release Instruction (Release Window) … Field: Lot (lot_id)"
What you see: after Release in the Release Lot window of a lot that holds owner units:
Validation Error
The operation cannot be completed:
- Create/update: a mandatory field is not set.
- Delete: another model requires the record being deleted. If possible, archive it instead.
Model: Owner Release Instruction (Release Window) (dscsa.lot.quarantine.owner.line)
Field: Lot (lot_id)
When: an Rx Tracking Manager releases the lot by hand, for example after resolving the differences of a late file (3PL-GBD-06), whether the owner row has a Recorded Instruction, a typed Reference, or nothing.
Cause: a product defect (PF-W15-01): the window's owner rows lose their lot and owner when they are saved, so the release can never be saved from the web client. Nothing is released and no instruction is recorded.
Remedy: no workaround in the screens.
- Resolve every discrepancy of the lot, so that nothing but the manual release is missing.
- Keep the owner's release instruction on file: Record an owner's instruction.
- Report the lot to your implementer. Releases the software makes by itself (a late file, a statement document or the owner's confirmation that clears the last hold) still work.
Who can fix it: your implementer (a product fix).
Error: "A supplier file is already recorded for …"
What you see:
A supplier file is already recorded for WH/IN/NNNNN (FILE-NAME).
When: Attach of an EPCIS file on a done receipt, in Release a data-pending hold with the supplier's late EPCIS file; also when the owner uploads a second file on its portal.
Cause: the receipt already has its supplier file. A done receipt takes one late file only; a corrected file can't replace it.
Remedy: nothing to do for the hold: the first file already released it (or its differences hold the lot: The lot stays quarantined after the data is recorded). If the supplier sent a corrected file because the first one was wrong, keep it as evidence in the discrepancies' resolution notes (Resolve the differences a late supplier file finds).
Who can fix it: Rx Tracking User or Manager.
Error: "None of the packages the file lists was received on …"
What you see:
FILE-NAME was not imported:
- None of the packages the file lists was received on WH/IN/NNNNN: is it the right file?
When: Attach of an EPCIS file on a done receipt (3PL-GBD-02), or an owner's upload on a done receipt (the receipt's chatter then says "… it was refused: …").
Cause: not one serial of the file was received on this receipt: the file belongs to another shipment (another receipt of the owner, or goods not received yet).
Remedy: resolution.
- Compare the file's PO number and serials with the receipt's Source Document and DSCSA Packages tab.
- Attach the file to the receipt it belongs to: a done receipt from that receipt, an open one as in Attach the supplier's EPCIS file to an owner's open receipt.
- Ask the owner or the supplier for this receipt's file.
Who can fix it: Rx Tracking User or Manager.
The Supplier Data Pending item was closed without data
What you see: a Supplier Data Pending discrepancy is Resolved, but its lot is still Quarantined; the discrepancy and the receipt no longer show Attach Supplier Data (on the discrepancy) or Record Owner Confirmation, and the red banner is gone. Record Owner Confirmation or the statement document on the receipt is refused with:
WH/IN/NNNNN has no supplier data pending.
When: after someone selected Mark Resolved on the item, in Work the Supplier Data Pending list.
Cause: a product defect (PF-A06-05): the core Mark Resolved button closes the item without recording any data and without releasing the lot. A late EPCIS file still imports, but releases nothing.
Remedy: workaround.
- As an Rx Tracking Manager, open the discrepancy and select Reopen. It is Open again, and the banner and buttons come back.
- Record the file, the statement document or the owner's confirmation (3PL-GBD-02, 3PL-GBD-03, 3PL-GBD-04).
Who can fix it: Rx Tracking Manager (step 1); then Rx Tracking User or Manager.
Warning: "… They become discrepancies when the receipt is validated." on a late file
What you see: the Supplier EPCIS File of a late file shows the yellow banner:
N serial(s) in this file are already in the package ledger (suspect product). They become discrepancies when the receipt is validated.
When: after Release a data-pending hold with the supplier's late EPCIS file, with a file that lists serials already in your records.
Cause: the banner is the core text written for files imported before the goods are received (PF-W15-02). On a late file the receipt is already done, and the Duplicate Serial discrepancies already exist.
Remedy: nothing to do about the banner. Open the file's Discrepancies smart button and work the Duplicate Serial rows as in Resolve the differences a late supplier file finds.
Who can fix it: Rx Tracking User or Manager.
The owner's upload was refused
What you see: the receipt's chatter has one of these notes from the owner's portal user, and nothing was imported:
The owner's portal user USER uploaded supplier file FILE-NAME; it was refused:
FILE-NAME was not imported:
- REASON
The owner's portal user USER uploaded supplier file FILE-NAME; it was refused because these serials are already expected on another receipt: SERIALS.
The owner's portal user USER uploaded FILE-NAME; it was refused: N files were already uploaded to this receipt in the last 24 hours (the limit is 10).
When: the owner uploaded its supplier's data on its portal (Record supplier data the owner uploaded through its portal). The owner saw the reason in red on its Receipts page; for serials expected elsewhere it saw only that "some serial numbers it lists are already expected on another receipt".
Cause: the file failed the same checks as a file you attach yourself (the REASON line: another buyer, another ship-to, no serial of
the file received here…), its serials are already announced on a receipt of another owner or of yours, or the owner reached the limit of
10 uploads per receipt in 24 hours.
Remedy: resolution.
- For a
REASON, find its entry: Troubleshooting: owner receipts and owner isolation (buyer, ship-to, custody seller, other refusals) or Error: "None of the packages the file lists was received on …". - For serials expected on another receipt, find that receipt (Inventory ‣ Rx Tracking ‣ Packages, search the serial) and check with the owner which shipment the file belongs to. Don't tell the owner the other receipt's owner.
- Ask the owner for the right file, or to send it by email, and attach it yourself (3PL-GBD-02 or Attach the supplier's EPCIS file to an owner's open receipt).
What the owner sees and does: Understand a refused upload and what to do next. Portal pages that end on an "Error 404" page or a bare "413 Request Entity Too Large" page leave no note on the receipt (PF-A09-02, PF-A09-06): see Troubleshooting: owner portal.
Who can fix it: Rx Tracking User or Manager, with the owner.
Error: "Choose open 'Supplier data pending' discrepancies …"
What you see:
Choose open 'Supplier data pending' discrepancies (DISC/YYYY/NNNNN).
When: Attach Supplier Data or Record Owner Confirmation on a Supplier Data Pending discrepancy, in 3PL-GBD-02 or 3PL-GBD-04.
Cause: the discrepancy is no longer open: someone recorded the data, the confirmation or a Mark Resolved after you opened the form.
Remedy: reload the page. If it is Resolved with data, nothing more is needed. If it was closed with Mark Resolved, see The Supplier Data Pending item was closed without data.
Who can fix it: Rx Tracking User or Manager.
Errors met only through imports and API calls
What you see: one of these, from an integration or a script rather than the screens:
A late supplier file is attached to a done receipt held for an owner (WH/IN/NNNNN is not one). Import it on the open receipt instead.
Record the owner's confirmation for one owner's receipts at a time.
When: a late file sent to a receipt that is not a done owner receipt; an owner confirmation recorded on discrepancies of several owners in one call.
Cause: the screens only offer done owner receipts for a late file and one receipt per confirmation, so these checks protect the other channels.
Remedy: send the file to the open receipt's import (or the done owner receipt), and record one owner's confirmation per call.
Who can fix it: whoever runs the integration.
Other refusals of a late file
What you see: "FILE-NAME was not imported:" followed by a line about the buyer, the ship-to location, the custody seller, a product the file announces that isn't a DSCSA product of yours, packages without a lot number, a file without serialized packages, or "FILE-NAME can't be read as an EPCIS 1.2 file: …".
When: Attach in 3PL-GBD-02.
Cause: the late file is checked as a file on an open owner receipt, plus the two late-file checks above.
Remedy: see Owner receipts and owner isolation: other refused files and the entries before it.
Who can fix it: Rx Tracking User or Manager, with the supplier.