The promote_scenarios macro updates the FSK_SCENARIO table prior to updating FSK_ROUTING_GROUP. This could cause a violation of the constraint R_66 that is placed on the FSK_SCENARIO table.

The R_66 constraint is defined below. Note that you might see intergrity violation messages in the log when the promote scenarios macro is executed.

ALTER TABLE FSK_SCENARIO
       ADD CONSTRAINT R_66
              FOREIGN KEY (routing_group_id)
              REFERENCES FSK_ROUTING_GROUP (routing_group_id)
              ON DELETE SET NULL;

Operating System and Release Information

A fix for this issue for SAS Anti-Money Laundering 2.1 is available at:

A fix for this issue for SAS Anti-Money Laundering 2.1.1 is available at: