Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
I doubt if there is any system variable which gives you that sort of information but you can read TSTC table with the ABAP name (SY-CPROG) and get the transaction code as an alternative.
Thanks for info. First of all we need to know the transaction, then we can do any thing. Table SHDTVCIU just gives information about original transaction and transaction variant.
Our transaction can be called directly or using transaction variant. We need to know "when it is called from transaction variant".
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
I had just the same problem/question. Maybe in the meantime you figured out a solution yourself. This is what I did.
Didn't check on the transaction code but on the variant linked to it. I used it in the validation rules. Via the assign you get the variant and you can do any checks you want.
Bluesky
