As RMG points out, it will work.
The way the EDI module in 4.6 works is that it looks at the qualifier from the EDI doc. If it is anything other than 01 or ZZ, it will look for a User Defined 1 value that matches the EDI identifier. Meaning if the qualifier is 12 it will look at User Defined 1, if the qualifier is 08 it will look at User Defined 1, etc. The EDI module, when figuring out which partner is the sender or receiver, never looks at any other identifier types–thus User Defined 2 and User Defined 3 are never used by the EDI module (in 4.6).
Your profile might look like this:
Profile XYZ
DUNS - 123456789
Mutually Defined - XYZ
User Defined 1 - 1112223333 (for qualifier 12 - phone)
User Defined 1 - 6661110100 (for qualifier 08 - UCC)
The EDI module will match to the appropriate profile. TN Console will prevent multiple User Defined 1 from having the same value.
Lastly, as I recall TN didn’t used to allow multiple external IDs of the same type for a given profile but I don’t remember what version had that limitation. There was a patch available that would allow it.
#edi#Integration-Server-and-ESB#webMethods