This release updates the Document EDI module, available to all sites, to allow documents files to be received into Expedient.
Expedent can be configured to receive Document XML in either Expedient format or Cargowise Universal Event format. Documents can be received via email, via SFTP, or to a local directory
Inbound Document EDI Configuration
Matching the Document to a Consol or Job
On receiving a Document XML file, Expedient will use the information in the file, to find the correct Consol or Job to save the document to. The Consol or the Job must have been registered within the last six months to successfully receive a document file
In the Expedient format Document XML, the sender can include the following references to help Expedient find the correct Consol or Job
- Receiver Job Number
- Receiver Consol Number
- External ID at Job Level
- Master Bill Number
- House Bill Number
In the Cargowise Universal event XML, the sender can include only the Master Bill or House Bill
Expedient will follow the following flow to try to locate the appropriate Consol or Job
Expedient will use the Document Code mapping in Administration -> Interface -> EDI Configuration -> EDI Configuration, Document > Inbound > Document Mapping, to save the file with an Expedient Document Code, save to the public or private folder to match default settings in Administration -> Document Management -> Document ID Masterfile, tick off required documents, and trigger linked events, as though the document has been manually added to the consol or job.
When a matching Consol or Job cannot be found
Expedient will use the references within the Document XML file, and the Inbound Document EDI Configuration to try to find the correct Import or Export, Consol or Job, including the Manifest EDI holding screens
If Expedient cannot locate a single matching Consol or Job, the Document details will be listed in Forwarding -> Inbound EDI -> Document EDI
If Expedient finds more than one possible match, the document details will also show in the Document EDI screen
If there are no references in the file, Expedient will move the document to this screen
This screen lists all the unmatched Document XML, with the oldest received document at the top.
Expedient continuously works through the list of unmatched documents to find a single matching Consol or Job. For example, if an overseas agent sends Document XML to accompany Manifest EDI, but the Document XML is received before the Manifest XML, Expedient will match the document to the House Holding record after it has been created, or match to the live Job when it exists.
Documents can be selected and assigned manually to specific Consol or Jobs from this screen. For example, if a set of documents has been received from an external party for a specific House Bill, use the ‘Show Search’ toolbar button to find all the documents with that house bill, e.g.
Use the Edit button under the list of search results
Enter the Level, Direction and Reference the documents should be assigned to e.g. Job, Export and Job Number
On OK, the Documents will be removed from the Document EDI screen and saved to the assigned location
Unmatched documents are automatically removed from the Document EDI screen 6 months after receipt. To change this setting, go to Administration -> Interface -> EDI Configuration -> Document EDI Advanced Configuration
Expedient can also provide a daily CSV report listing unmatched documents, via User Option ‘DOCEDIUNASSI’ in Administration -> Corporate -> Users Masterfile