I'm not sure I fully understand the use case for such a design, but this seems to mean that you'd want to run the listed transactions in a designated area of, say, the SMEN screen for which the main flavor was created.
Technically you could run a transaction in an HTML viewer embedded into your SMEN flavor, since the transaction can be included via a URL. Whether that is a good thing to do is debatable...
If you are after a breadcrumb-like sequence, you could have flavors for the individual transactions that mimic this design, including transaction buttons on the left to navigate to the other transaction. I suppose the user would only run one transaction at a time... so there is no need to see three transactions at the same time.
You could have a flavor for each transaction, with corresponding buttons on the left side that lead to the other transactions as the business process requires. If the default flavors are configured correctly for the users, going to VA02 or VA03 will activate the right flavor with these navigation buttons.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.