To allow import and export of manifest data Agents must be mapped to ensure manifest data is captured correctly.
The set up options are available in the Air Import Forwarding and the Sea Import Forwarding > Manifest EDI
Details of the Agents, Forwarders and Brokers receiving and sending Manifest EDI must be set up in the Agent Mapping screen.
Adding an Overseas Agent
If you are an Agent use the Agent Mapping screen to set up the Oversea Agents you want to receive import Manifest EDI from and send export Manifest EDI to.
|
Field Name |
Description |
Validation |
Default |
|
|
Details |
||||
|
What is the reason for mapping this agent? |
Select the appropriate reason for mapping the agent from the pull down menu – “Receiving Import and/or sending Export EDI Manifests from an O/S Agent” |
Mandatory |
Blank |
|
|
O/S Agent Code |
This is your customer code for the agent. Use the |
Mandatory |
Blank |
|
|
O/S Agent Ref |
This is reference code for the agent. In Manifests imported from the Agent this is the code they use to identify themselves. This code will also be used in the manifests exported to the agent to identify the recipient. |
Mandatory |
Default to match O/S Agent Code |
|
|
Import Manifest Information |
||||
|
Do we receive Import EDI files from them? |
Select Yes from the drop down list to allow the import of the agents Manifest EDI |
Mandatory |
Yes |
|
|
File Source |
Select the file format the Agent will send to you. What system does the agent use to produce the Manifest EDI? Please request the XSD from Expedient Software to pass to your Overseas Agent for their information if they do not use one of the listed formats. Once selected the email address the Overseas Agent should send the Manifest EDI to is displayed. Please advise your Overseas Agent to use this email address. If your Overseas Agent is not able to supply the Manifest EDI in the Expedient format or any other format listed please send an example of the agent’s Manifest EDI to Expedient Software for investigation using Support Tracker. |
Conditional on Send Export EDI is Yes |
Blank |
|
|
Export Manifest Information |
||||
|
Do we send Export EDI Files to them? |
This indicates if you want to send Export Manifest EDI to the Overseas Agent |
Mandatory |
No |
|
|
Sender Ref |
This is your reference to the Overseas Agent so they know the Export Manifest EDI came from you. The Sender Ref is usually the code the Overseas Agent uses for your office. |
Conditional on Send Export EDI is Yes |
Blank |
|
|
Export File Trigger |
This indicates the trigger for sending the Export EDI Manifest automatically. Select from the pull down menu. |
Conditional on Send Export EDI is Yes |
ETD |
|
|
Days |
This is the number of days after ETD the Manifest EDI will be sent |
Conditional on Export File Trigger is ETD
|
0 |
|
|
Import EDI |
||||
|
Contacts to receive alerts regarding the EDI Import Manifests (Successful/Errors) |
This table lists the contacts at the Overseas Agent and internally to receive email notifications when new or updated Import Manifests have been received and if there are any errors processing the data. There must be at least one internal User to receive email notifications. |
Active Personnel/Active Users |
Blank |
|
|
Contact Type |
Select the appropriate contact type from the pull down menu |
Mandatory |
O/S Agent |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the Personnel in the Customer Masterfile or the User Masterfile for internal Users |
N/A |
Blank |
|
|
Associated Port |
If a Port Code is assigned to the Manifest Contact, then the user will be notified via email when a XML file is loaded or updated into the Holding Screen for that specific Port. If no Port Code is assigned then the user will receive an email notification for ALL Ports. If Contact Type = O/S Agent, the associated Port Code matches to the Origin Port in the file. If Contact Type = Internal, the associated Port Code matches to the Destination Port in the file. |
Optional |
Blank |
|
|
Export EDI |
||||
|
Email Addresses to receive the EDI Export Manifest File |
This table lists the O/S Agent contacts and any internal Users that receive the Export Manifest EDI. |
Active Personnel/Active Users |
|
|
|
Contact Type |
Select the appropriate contact type from the pull down menu |
Mandatory |
O/S Agent |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the Personnel in the Customer Masterfile or the User Masterfile for internal Users |
N/A |
Blank |
|
|
Contacts to receive EDI Export Manifest errors |
This table lists the internal Users to receive email alerts when there is a problem sending the Export Manifest EDI. O/S Agent contacts can also be listed here. |
Active Users/Active Personnel |
|
|
|
Contact Type |
Select the appropriate contact type from the pull down menu |
Mandatory |
Internal |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the User Masterfile for internal Users or the Personnel in the Customer Masterfile for the Overseas Agent. |
N/A |
Blank |
|
|
Associated Port |
If a Port Code is assigned to the Manifest Contact, then the user will be notified via email when a XML file is loaded or updated into the Holding Screen for that specific Port. If no Port Code is assigned then the user will receive an email notification for ALL Ports. If Contact Type = O/S Agent, the associated Port Code matches to the Origin Port in the file. If Contact Type = Internal, the associated Port Code matches to the Destination Port in the file. |
Optional |
Blank |
|
Adding a Broker
If you are a Forwarder use the Manifest EDI Agent Mapping screen to set up the Broker you want to send import Manifest EDI to.
|
Field Name |
Description |
Validation |
Default |
|
|
Details |
||||
|
What is the reason for mapping this agent |
Select “Sending a shipment to a local Broker” |
Mandatory |
Blank |
|
|
Agent Information |
||||
|
Broker Code |
Select the customer code for the Broker. Use the |
Mandatory |
Blank |
|
|
Sender Ref |
This is reference code used in the Import Manifests sent to the Broker to identify the source of the file i.e. you. |
Mandatory |
Default to match Broker Code |
|
|
EDI Contacts |
||||
|
Email Addresses to receive the EDI File |
This table lists the Broker contacts and any internal Users that receive the EDI. There must be at least one contact at the Broker. |
Active Broker Personnel /Active Users |
|
|
|
Contact Type |
Select the appropriate contact type from the pull down menu |
Mandatory |
Broker |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the Personnel in the Customer Masterfile or the User Masterfile for internal Users |
N/A |
Blank |
|
|
Internal Responsible Contacts (for errors) |
This table lists the internal Users to receive email alerts when there is a problem sending the EDI to the Broker. There must be at least one User listed to receive error messages. |
Active Users |
Blank |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the User Masterfile. |
N/A |
Blank |
|
Adding a Forwarder
If you are a Broker use the Manifest EDI Agent Mapping screen to set up the Forwarder you want to receive import Manifest EDI from.
|
Field Name |
Description |
Validation |
Default |
|
|
Details |
||||
|
What is the reason for mapping this agent? |
Select “Receiving a shipment from a local Forwarder” |
Mandatory |
Blank |
|
|
Agent Information |
||||
|
Forwarder Code |
Select the customer code for the Forwarder. Use the |
Mandatory |
Blank |
|
|
Sender Ref |
This is reference code used in the Import Manifests EDI sent by the Forwarder to identify the source of the file. |
Mandatory |
Default to match Forwarder Code |
|
|
Import Manifest Information |
||||
|
Do we receive Import EDI files from them? |
Select Yes from the drop down list to allow the import of the Forwarder’s Manifest EDI |
Mandatory |
Yes |
|
|
File Source |
Select the file format the Forwarder will send to you. What system does the Forwarder use to produce the Manifest EDI? Please request the XSD from Expedient Software to pass to your Forwarder for their information if they do not use one of the listed formats. Once selected the email address the Forwarder should send the Manifest EDI to is displayed. Please advise your Forwarder to use this email address. If your Forwarder is not able to supply the Manifest EDI in the Expedient format or any other format listed please send an example of the Forwarder’s Manifest EDI to Expedient Software for investigation using Support Tracker. |
Conditional on Receive Import EDI is Yes |
Blank |
|
|
EDI Contacts |
||||
|
Contacts to receive alerts regarding the EDI (Successful/Errors) |
This table lists the contacts at the Forwarder and internally to receive email notifications when new or updated Import Manifests have been received and if there are any errors processing the data. There must at least one internal User to receive email notifications. |
Active Personnel/Active Users |
Blank |
|
|
Contact Type |
Select the appropriate contact type from the pull down menu |
Mandatory |
Forwarder |
|
|
Contact Name |
Use the |
Mandatory |
Blank |
|
|
Email Address |
This is populated when a Contact Name is selected. This field cannot be updated in this screen. If the email address is incorrect please update the Personnel in the Customer Masterfile for the Forwarder or the User Masterfile for internal Users |
N/A |
Blank |
|
to zoom on active Overseas Agents.