LCB Contact information
Regulatory and reporting: Examiners at email@example.com or 360-664-1614
Compliance: Enforcement and Education division at firstname.lastname@example.org
Technical support: IT Helpdesk at email@example.com or 360-664-1776
When loading the Area File, if you have already loaded the area file into the CCRS system, it will send you an error email. We have built this area file with only one room called Sales Floor and that room will not change over time. You only need to load the Area file once, the first time you start working with CCRS to not receive this error.
When loading the Strain File, if you have already loaded strains into the CCRS system, it will send you an error email. Per the LCB:
As reflected on page 41 of the CCRS User Guide the LCB statement reads:
If Duplicate Strain/StrainType error message is received, assumption is that strain exists in the system. Reporting entity does not have an action to take for correction.
Note: This same scenario will occur when completing a plant CSV. Strain is required on both Plant and Inventory but the Strain CSV does not need to be submitted if the Strain already exists in the system.
When loading the Product File, if you have already loaded products into the CCRS system, it will send you an error email. We have initially built this product file to be an insert-only file. This means once your products are loaded into CCRS, if you load it again it will provide you with the “Duplicate External Identifier" message. We advise you to always load this product file because any new products created will get added into the CCRS system
When loading the Inventory File, if you have already loaded inventory into the CCRS system, it may send you an error email. We have initially built this inventory file to be an insert-only file. This means once your inventory is loaded into CCRS, if you load it again it will provide you with the “Duplicate External Identifier" message. We advise you to always load this inventory file because any new products created will get added into the CCRS system.
From what we have seen via our customer feedback, the checksum issue in files means some name or description data you manage in our back office (like strain name or product description) has a comma or line return in that data, which causes the file to have two rows for one line of data and therefore fails to submit. We advise that you refrain from using commas or line breaks in any name or description data in Greenbits.
Per the LCB: There could be more than one reason for which a file receives a CheckSum error. Check sum should be the number of records being loaded in the CSV report. There may be residual data beneath the rows that follow actual data records. In those instances, delete all the blank rows beneath the records that contain detail.
While we agree that this may be a potential issue, we have tried to prevent this situation from occurring. Please reach out to our support team if any of your errors contain a check sum message.
If you receive error FromInventoryExternalIdentifier: Invalid To InventoryExternalIdentifier.
FromInventoryExternalIdentifier: Invalid To InventoryExternalIdentifier or any combinations of these two means the manifest was not imported into CCRS. This is an acceptable error for the first load if they never added manifests from Leaf into CCRS. This error will start to go away when all manifests are loaded into CCRS.
LCB Response: This is not an acceptable error message to set aside. Manifests are not being “loaded” in CSV’s. The manifest is required to ensure that licensees remain compliant with the expectations outlined in WAC 314-55-085. The detail on the FromInventoryExternalIdentifier comes from the detail in CSV reports that has been loaded in more than one CSV file across the licensee base. If the statement Invalid FromInventoryExtneralIdentifier or Invalid To InventoryExternalIdentifer is received it is more likely that there is an entry error or that the required detail has not been successfully uploaded into the CCRS licensee record as required.
This error can be received if a licensee is completing reporting prior to the sending licensee uploading their CCRS reports. Another reason this error may be received is there are spelling errors between the two csv files.
Since this information is contingent on another license completing their CCRS update, a working solution is having the seller send the external identifiers listed on the sales.csv to the buyer after they have completed their upload, minimizing the rate of receiving the error and embedding a standard business operation question to ask the sender if they have already loaded the appropriate ID’s into CCRS (not the manifest).