Frequently asked questions

Generic EDI queries

See EDI Core FAQ for generic queries

Fixing Staging-to-Target EDI errors

The following table describes a few staging errors that could be experienced with Freight forwarder inbound documents at the staging to target step. Short description of possible fixes are discussed. After fix, reset status on the staging record and either manually process again or leave for batch to process.

Note: % contains staging data for the record

Voyage creator

Error message	Method to fix
Duplicate shipment reference found on shipment: %	Can be Warning or Error level based on document setting Duplicate tolerance. • Warning will create a new Voyage with same booking reference. • Error level will not create a voyage, review field Booking reference in staging record.
Item not found: %	Based on document setting Item id source, review field: • Bar code where Item id source is set to GTIN or Barcode. • Item number where Item id source is set to Our item number or External item number
No mapping found for Customs broker %	Staging record field Customs broker contains a vendor not setup in the Customs broker mapping assigned to the Trading partner.
Over delivery not allowed on EDI line %	Staging record’s quantity in the staging record’s unit is more than remaining on the purchase or transfer order line and document setting Allow purchase order over delivery or Allow transfer order over delivery doesn’t allow overdelivery. Review staging’s quantity and unit and either increase purchase or transfer order line’s open quantity that can still be added to a voyage or if overdeliveries are allowed, update the trading partner to use a document setting that allows overdelivery.
Shipment status % indicates shipment cannot be modified	When document setting Duplicate tolerance is set to Accept, EDI allows the “additional” voyage lines to be added to an existing open voyage. The voyage’s Shipment status is considered open if it allows modification. This error will be received if the staging Booking reference is a duplicate and the existing voyage’s shipment status is not open for modification. Review it it should be added to existing voyage and update status to add, or edit staging’s Booking reference if it should create a new voyage.
Unable to find journal template for line: %	EDI couldn’t find a Landed cost journey template based on the staging record’s From port, To port and Delivery mode as per calculation.
Unable to locate source document lines	EDI couldn’t find the source D365 document based on staging record’s Number, Reference (Purchase order or Transfer) and Item number. Review the Purchase / Transfer order number is still available to add to a voyage. Also confirm the Item number match the Item id source (Our item number, external item number, GTIN or Barcode) allocated in the setting profile.

Voyage tracking

Error message	Method to fix
Shipment not found: %	Based on document setting Voyage Id source, the staging record’s Voyage is either internal voyage id or the voyage’s booking reference and EDI couldn’t find the voyage in D365 Landed cost. Review staging field Voyage and either edit if incorrect or ensure voyage is created if field is correct. Document setting could also be the issue, verify if trading partner refers to internal id or their booking reference and update document setting allocated to trading partner if incorrect.
No shipment activity lines found for shipment: % container: %	Review if the staging record’s Activity is setup in the activity mapping that is assigned to the trading partner.
Date qualifier % not recognised	Review if staging record’s Date qualifier is setup in the document setting Actual or Estimated date qualifiers.