topic Re: fields Mandatory, Hidden or Display in Application Development and Automation Discussions

fields Mandatory, Hidden or Display

Former Member — Wed, 19 Sep 2007 13:45:47 GMT

How to use Transaction Variants to make your fields Mandatory, Hidden or Display ?

Re: fields Mandatory, Hidden or Display

Former Member — Wed, 19 Sep 2007 13:48:02 GMT

Steps :-

Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.

Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.

Create and change the Zxxx area menu with the new transaction variant. In this way, the user does have to remembers any extra transaction codes.

In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate asstandard variant)

Pls walk through this link.

http://www.sap-basis-abap.com/sapbs010.htm

An example for using transaction variant (restricting the field displayfor CO11N - Goods movement) :-

If you want to restrict changes to the fields in Goods movement forone group of users.

1. Create a transaction variant for CO11N

2. Create a new transction code for the transaction variant and assign an authorization object to it

3. Divide the users into this two transaction code. Those who can change the field using CO11N. For those that have limited field change, give them the authorization for ZCO11 (this is a new transaction code you have to create).

Re: fields Mandatory, Hidden or Display

Former Member — Wed, 19 Sep 2007 13:51:14 GMT

Use the Tcode <b>SHD0</b>

Go to this place enter the SAP std tcode to which you wants to create a Transaction variant and enter variant name

press create button

it will go through the screens of that std Transaction recording all the screen variants

and then save

it creates a transaction variant with Screen variants

then goto each screen variant there itself and make the fields as per your requirement mandatory, invisible, output only etc

then save.

Now go to the SE93 create a new Tcode(variant transaction 4th radiobutton)

enter the Sap std Tcode and the Transaction varient name there and save the tcode

now if you execute this Tcode you will see all the fields as per your requirement

Reward points if useful

regards

Anji

Re: fields Mandatory, Hidden or Display

Former Member — Wed, 19 Sep 2007 13:52:09 GMT

Hi,

we can create Transaction Variants Using SHD0 Transaction.

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).

Regards

vasu