Only logical explanation for me is that you created parameter transactions to start the generated screen programs of SE16 and then activated the optional OSS note to check S_TCODE in the screen already.
Not a well thought out plan. Rather remove the S_TCODE check implemented and use proper parameter transactions for SE16 itself or proper application reporting.
An illogical explanation would be that the transactions hard coded an S_TCODE 'SE16' just for the hell of it but is not needed. Remove it or replace it with a proper check object.
Cheers,
Julius
