I thought about the workaround you are suggesting but, appart from that maybe it doesn't seem to be so optimal, also, calling it in a loop causes "a violation of Primary Key" in a system table created and managed by the own SAP DataServices during the execution, as you can see in the post below:
Violation of Primary Key Constraint while using Address Match Transform
Anyway, do you know if there is a way to use/configure the Match Transform (or another transformation method) so that it doesn't make matching groups (but just an association 1-N between the input data and the master table records for each input data record to get pure similarity percentages and be able to obtain the best option from the master table)?
Thanks again and best regards,
José