on 08-28-2018 7:22 AM
Hello,
I have seen in many projects that there are z t codes created for standard T codes. For example for creating sales order , VA01 is used but in some projects ZVA01 is used.
if authorization control is the reason then that can be controlled through Authorisation profiles by using standard T code VA01 only.
why the need for ZVA01 or any Z t code representing a standard transaction.
regards
sachin
Transaction variants is a possible reason, but there are others. Usint a custom T-Code can also be useful to activate/deactivate custom functionality in exits and badis. For the developer is very easy: if T-Code is ZVA01, run custom code; otherwise, run only standard code. In case you are facing a problem, you just need to compare VA01 with ZVA01. If the problem cannot be reproduced in the standard transaction, then you have a problem in your custom code and know where to look for the solution. If the problem happens also when using the standard transaction, then you know the issue is in SAP standard code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As venkatramesh.v said, those T codes might have created using SHD0, and it is used to make fields hide, mandatory, Output only......
Check standard VA01 and custom T code to see the differences.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
screen variant & transaction variant tcodeSHD0 may be used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Add the keyword 'variant' to your search.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.