Instead of creating a matrix and select the best fit, why not let SAS take care of that? That is exactly what SQL does when it joins (creates all possible combinations of rows that fit the ON clause): proc sql; select a.ctr, /* other columns */ case /* case statements to calculate score */ end as score from a join b on a.ctr=b.ctr group by a.ctr having calculated score=max(calculated score) ; If you need further help, you will have to supply some example data (preferably as data step code). ... View more

The EG Application model for automation is inherently not visible. It does not support scripting with the user interface showing. ... View more

There are always moments where the helpers and wizards run out of steam, and this is one of them. You cannot loop a node in a process flow back to another node in the same flow. And a node can only be present in one process flow. Using it in another process flow means making a separate copy in that flow that no longer is tied to the original. To run code repeatedly in one execution, you need to use macro language or other means like CALL EXECUTE, and that means code nodes. To reuse code, you have to store it in a .sas file and %INCLUDE that wherever needed. ... View more