EDI Freight forwarder
EDI Freight forwarder Setup
EDI Freight forwarder Setup
This section provides a short overview of the required prequisites for setting up EDI for Freight forwarder landed cost.
The Trading partner fields are used to describe how the prequisites setups are allocated to an EDI Freight forwarder landed cost.
Users can access the form by navigating to EDI > Setup > Trading partners
Trading Partner Setup - Quick Summary:
| Setup | Short description | Setup path |
|---|---|---|
| Options | ||
| Connection profile | Ability to override the default EDI connection profile on Trading partner level. If blank, default EDI connection will be used. Default EDI connection is determined by: • Outgoing documents: Connection profile setup on EDI > Setup > EDI parameters • Incoming documents: All active connection incoming paths as setup in Connections. |
EDI > Setup > Connection setup |
| Cleanup profile | Ability to override the default Cleanup profile (setup on Shared EDI parameters) on Trading partner level. If blank, default Cleanup profile will be used as setup on EDI > Setup > EDI shared parameters | EDI > Setup > Cleanup profile |
| Container mapping | ||
| Container type | Container type identifiers | EDI > Freight forwarder landed cost setup > Shipping container type mappings |
| Measurement unit | Shipping measurement unit mapping | EDI > Freight forwarder landed cost setup > Shipping measurement unit mapping |
| Journey mapping | ||
| Port | Shipping port mapping | EDI > Freight forwarder landed cost setup > Shipping port mapping |
| Port qualifier | Shipping port qualifier mapping | EDI > Freight forwarder landed cost setup > Shipping port qualifier mapping |
| Mode of delivery | Mode of delivery mapping | EDI > Freight forwarder landed cost setup > Modes of delivery mapping |
| Activity | Activity mapping | EDI > Freight forwarder landed cost setup > Activity mapping |
| Other mappings | ||
| Customs broker | Customs broker mapping | EDI > Freight forwarder landed cost setup > Customs broker mapping |
| UOM | Unit of measure mappings for in- and outbound documents | EDI > Setup > UOM mapping |
| Outgoing documents | It brings the document template, mappings, settings profile together to enable the document for the trading partner |
|
| EDI Document type | Each applicable outbound document type | EDI > Setup > Document types |
| Template | Document type template | Templates on EDI > Setup > Document types |
| Setting profile | Settings profile | Setting profiles on EDI > Setup > Document types |
| File name setup | Outbound file name | EDI > Setup > Document types |
| Connection profile | Ability to override the default EDI connection profile on document level. If blank, the trading partner’s Connection profile will be used. | EDI > Setup > Connection setup |
| Cleanup profile | Ability to override the default Cleanup profile on document level. If blank, the trading partner’s Cleanup profile will be used. If Trading partner’s Cleanup profile is blank, the default Cleanup profile on EDI shared parameters will be used. | EDI > Setup > Cleanup profile |
| Acknowledgement | An Inbound Functional Acknowledgement is required from the trading partner for the outgoing document. Note: Also required to setup the Functional acknowledgement inbound document under Incoming documents. | Y/N |
| Enabled | Ability to enable/disable document type for Trading partner | Y/N |
| Incoming documents | It brings the document template, mappings, settings profile, validation and filename mask together to enable the document for the trading partner | |
| EDI Document type | Each applicable inbound document type | EDI > Setup > Document types |
| Template | Document type templates defined for the document type | Templates on EDI > Setup > Document types |
| Setting profile | Settings profiles defined for the document type | Setting profiles on EDI > Setup > Document types |
| Validation profile | Validation profiles defined for the document type | EDI > Setup > Document types |
| Search mask | A file mask is used to match files in the document type’s defined directories | |
| Connection profile | Ability to override the default EDI connection profile on document level. If blank, the trading partner’s Connection profile will be used. | EDI > Setup > Document types |
| Cleanup profile | Ability to override the default Cleanup profile on document level. If blank, the trading partner’s Cleanup profile will be used. If Trading partner’s Cleanup profile is blank, the default Cleanup profile on EDI shared parameters will be used. | EDI > Setup > Cleanup profile |
| Acknowledgement | Trading partner requires an Outbound Functional Acknowledgement for the incoming document. Note: Also required to setup the Functional acknowledgement outbound document under Outgoing documents. | Y/N |
| Enabled | Ability to enable/disable document type for Trading partner | Y/N |