What's the Difference FacilityLocation vs FacilitySMDGLocation ?

[cmsdroff]

The DCSA Facility entity identifies 2 facility types:

• BIC
• SMDG

Both of these are child codes of the UNLOCODE and based upon the UNLOCODE as the first 5 characters. For BIC and SMDG they then provide the 'extension' code to identify the facility. i.e. GBLIVJMDA (BIC) or DEHAMHHLA (SMDG)

The facilityLocation covers both BIC and SMDG by using the attribute to differentiate facilityCodeListProvider being set as either BIC or SMDG respectively.

The facilitySMDGLocation is a duplicate of the above with the UNLOCODE mandatory instead of optional (added later), and for both supported facility types in DCSA the UNLOCODE is mandatory, but everything else is the same, so why separate ?

This now leads to 2 places to add the SMDG code, giving an unnecessary choice and adding additional mapping logic.

I would suggest only having 1 i.e. facilityLocation and use the facilityCostListProvider to identify as this matches the model, struggle to see why this isn't sufficient?

[HenrikHL]

Hi @cmsdroff,
Sorry for the late reply :-(

The facilitySMDGLocation is a duplicate of the above with the UNLOCODE mandatory instead of optional (added later), and for both supported facility types in DCSA the UNLOCODE is mandatory, but everything else is the same, so why separate ?

This was a request from the Carriers as in some cases they do not want to have to specify the facilityCodeListProvider as being SMDG. This is specifically in OVS and JIT where only SMDG facility codes are needed. Prior to the facilitySMDGLocation these two APIs contained the facilityCode and facilityCodeListProvider...