Example: For mrbp and mir6 transactions, object used is BUS2081, but I want to differentiate the logic basis of transaction code inside the workflow itself.
As a general comment I would warn against this approach. Hinging the logic of your workflow against a name of a program (or T-Code) is not really robust as your workflow will break if SAP changes their code (they may move the event raising code to another Function Group). I understand it's not always possible, but isn't there another application level field you could use which determines which logic you should execute?
Dig Deeper on SAP workflow development
Related Q&A from Alon Raskin
Find out how to configure clients so that the same version of an SAP workflow item is used when the workflow is triggered in separate clients. Continue Reading
An SAP user has created a user decision step in an SAP workflow item and wants to know how an end user can send an attachment to other users. Continue Reading
A SearchSAP.com reader wants to know how to hide the forward button in an SAP Business Workplace toolbar. Continue Reading