Troubleshooting: configuration
Core module For: Administrator, Compliance manager Checked on 18.0.0.2.0
What to do when the DSCSA settings, the company or warehouse GLN, the delivery emails or portal access don't behave as expected. Entries are ordered from the most frequent. Refusals that name access rights ("Only DSCSA users can …") are in Troubleshooting: access, companies and setup.
The DSCSA (Rx Tracking) block isn't in the settings
What you see: Inventory ‣ Configuration ‣ Settings opens, but searching DSCSA shows "No setting found"; or
Inventory ‣ Rx Tracking ‣ Settings (in the Configuration section) opens a settings page with only General Settings in the left
column.
When: in Open the DSCSA settings of a company.
Cause: the block is shown only to a user who has all three rights: Administration: Settings, Inventory Administrator and Rx Tracking Manager. Without Rx Tracking Manager the Inventory settings show without the block. Without Inventory Administrator the page has no Inventory settings at all, even when the Rx Tracking ‣ Settings menu is shown (known issue PF-W02-01).
Remedy: resolution.
- Ask an administrator to open your user in Settings ‣ Users & Companies ‣ Users and, on the Access Rights tab, set Rx Tracking to Manager, Inventory to Administrator and Administration to Settings. See Give staff the right Rx Tracking access.
- Reload the page, then open the settings again.
Who can fix it: Administrator (Administration: Settings).
Error: "You are not allowed to access 'Config Settings'"
What you see:
Access Error
You are not allowed to access 'Config Settings' (res.config.settings) records.
This operation is allowed for the following groups:
- Administration/Settings
Contact your administrator to request access if necessary.
When: a user without Administration: Settings opens the settings, for example from a bookmark or a link, in Open the DSCSA settings of a company. Such users have no settings menu.
Cause: only users with Administration: Settings may open any settings page, the DSCSA block included.
Remedy: resolution. Ask an administrator to give you Administration: Settings (with Inventory Administrator and Rx Tracking Manager), or to change the setting for you. For Odoo's access errors in general, see Error: "You are not allowed to access ... records".
Who can fix it: Administrator (Administration: Settings).
Error: "GLN '…' has an invalid check digit"
What you see: a dialog (titled "Validation Error" in the settings, "Oh snap!" on a form) with one of:
GLN 'DIGITS' has an invalid check digit: the last digit should be EXPECTED, not TYPED. Check for a typing or scanning error.
GLN 'DIGITS' must have 13 digits, it has COUNT.
GLN 'TEXT' must contain digits only.
When: saving a GLN in Set the company GLN and GS1 prefix length or Give a warehouse its own GLN. A trading partner's GLN gives the same messages.
Cause: a GLN has exactly 13 digits and its last digit is a check digit computed from the other twelve. A typing error, a missing or extra digit, or a letter makes it invalid. Spaces are allowed and removed.
Remedy: resolution.
- Close the dialog: in the settings select Close; on a form select Stay here (or Discard changes to keep the saved value).
- Enter the GLN again, as GS1 US assigned it, and save.
Who can fix it: the user changing the setting: for the company GLN, an administrator with Administration: Settings, Inventory Administrator and Rx Tracking Manager; for a warehouse GLN, an Inventory Administrator.
Error: "The GS1 company prefix length must be between 6 and 12"
What you see:
The GS1 company prefix length must be between 6 and 12 (it is NUMBER). Leave it empty to use the default of 7.
When: saving GS1 prefix length in Set the company GLN and GS1 prefix length.
Cause: a GS1 Company Prefix has 6 to 12 digits; another number can't be right.
Remedy: resolution. Select Close, enter the length of your GS1 Company Prefix, or 0 for the default of 7 (an empty field shows
0), and save.
Who can fix it: Administrator with Administration: Settings, Inventory Administrator and Rx Tracking Manager.
The delivery email has no DSCSA files
What you see: a delivery of DSCSA products that is Done has no confirmation email in its chatter, or the email has only the delivery slip,
without T3-….pdf and EPCIS-….xml.
When: after Send the DSCSA files with delivery confirmation emails was set up.
Cause: one of:
- Email Confirmation (in Shipping) is off: Odoo sends no delivery email at all.
- DSCSA files in delivery emails is off for the delivery's company: the email has only the delivery slip.
- The delivery has no DSCSA products, so it has no DSCSA document and no files.
- The delivery's DSCSA document has no EPCIS file: only the T3 report is attached. See Handle a document posted without an EPCIS file.
Remedy: resolution for the next deliveries. Turn both options on and save: see Send the DSCSA files with delivery confirmation emails. For a delivery already Done, the customer downloads the files from the portal, or you send the document from its record. See Send one document's link to a customer.
Who can fix it: Administrator with Administration: Settings, Inventory Administrator and Rx Tracking Manager.
Error: "The contact "…" does not have a valid email"
What you see: a dialog titled "Invalid Operation" after Grant Access, with one of:
The contact "CONTACT-NAME" does not have a valid email.
The contact "CONTACT-NAME" has the same email as an existing user
When: in Give a customer portal access to its DSCSA documents.
Cause: a portal user signs in with their email address, so it must be a valid address that no other user already signs in with. After the message, the contact's line shows no Grant Access until the address is valid, and no portal user is created.
Remedy: resolution.
- Select Close.
- In the Portal Access Management dialog, correct the address in the contact's Email column.
- Select Grant Access again. The dialog saves the corrected address on the contact when access is granted; selecting Close without granting leaves the contact's address unchanged.
Who can fix it: Administrator (Administration: Settings).
Documents show an empty Transaction Statement or have no EPCIS file
What you see: outbound DSCSA documents posted after a settings change print no Transaction Statement on their T3 report, or have no EPCIS file.
When: after someone saved an empty Transaction Statement or EPCIS legal notice in Review the Transaction Statement and the EPCIS legal notice.
Cause: the settings accept empty texts without a warning (known issue PF-A01-01). Each document keeps the texts in force when it was created, so documents posted while a text was empty keep it empty, and documents posted while both were empty have no EPCIS file.
Remedy: resolution for the next documents only.
- Put the texts back (the defaults are in the DSCSA settings reference) and select Save.
- For documents already posted, see Handle a document posted without an EPCIS file: posted documents can't be changed.
Who can fix it: Administrator with Administration: Settings, Inventory Administrator and Rx Tracking Manager.