Warnings and errors because of unmapped addresses
When booking confirmations are received in Scope via the SeaCarrier EDI portals, some carriers do not use unique Partner IDs (“UIDs”) that could be used to create a mapping in Scope. Until now, unstructured one-off addresses for container depots and container terminals could not be permanently linked to partner codes in Scope, which meant that these one-off addresses triggered warnings in Main Transport on the General tab of the shipment because the address structure was missing. The problem was exacerbated when, instead of a warning, an error was displayed because, for example, a location (town) for a depot or terminal was not recognized at all.
Whilst this could be temporarily corrected manually by entering a partner code, this was subsequently overwritten when the next booking confirmation arrived from the ocean carrier.
The Solution
With the new function in Sea Freight Export FCL, we are putting an end to this situation. If you now receive a SeaCarrier EDI booking confirmation in a Sea Freight Export FCL shipment containing addresses without a UID, the mapping can still be created permanently, as Scope can now establish the one-off mapping via the new EDI profile “OCE” (which stands for Ocean Carrier EDI in Scope).
The system will notify you within the shipment if any mappings are missing due to a received SeaCarrier EDI booking confirmation.
Switch to the “OCE” EDI profile, go to the “Missing Mappings” tab, and link the displayed one-off addresses to your partner so that, upon receipt of future SeaCarrier EDI booking confirmations for the same container depot and/or container terminal, Scope can automatically perform the mapping itself. 
Please note, however, that the link must be established for each ocean carrier, as is already the case for addresses with a UID. You must create any missing partner codes for depots and terminals using the existing function so that these partner codes are permanently available in Scope.