How to assign screen variant to transaction variant

[Former Member]

Hi ALL

I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT , PLS GUIDE ME ON THIS ITS IMPORTANT

[mayur_priyan]

This message was moderated.

[Manoj_Mahajan78]

Sunaina,

Transaction Variant:

Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.

Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.

You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.

Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.

The system will prompt to assign a package and request enter the necessary values.

Crux:- you just make fields as display, or 'supress', knowing your requirements

Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.

You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.

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

• Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).

o Next allocate the transaction variant to this variant transaction.

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

One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.

Hope this Clarifies your Doubt and Please Reward If Really Helpful

Regds

MM

[Former Member]

Hi All

Well i have created a screen variant and i want to assign screen variant to transaction varaint , cos it get error that screen variant i snot assigned to transaction variant , some one pls guide me how to assign screen variant to transaction variant

Regards

suvin

[avinash_gupta]

Very Nice explanation, and very useful at times when you need it as this topic is not in everyday use, it is easy to forget.

[Former Member]

Hello Sunaina,

Screens variants are generally used in simplifying the screens.

When you run a transaction you can provide values to fields in advance.

Or, you can hide and change the ready-for-input status of fields

A screen variant can hold field values and properties for a single screen. You can assign screen variants to transaction variants. For this you use SHD0 transaction.

For example, you want to permit certain users to view blocked invoices, but you do not want them to release. There is a transaction MRBR that shows all the blocked invoices, but this transasction also shows gives options and icons to permit release.

In order to remove such option of release together with that icon, you can create screen variant and assign to this transaction MRBR. In this screen variant you hide the option of release. The screen variant can be assigned to those users.

Field Status variants (FSV)are associated, generally with the GL accounts where control which field to be displayed, available for change etc when that GL is called.

FSVs are not available for any screen. Screen variant are available for all screens and transaction.

<b>REWARD POINTS IF HELPFUL</b>

Regards

Sai

[Former Member]

Hi Sunaina

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.

Reward if useful to u

[Former Member]

hi

check this link