transaction variant

Former Member — Mon, 19 May 2008 09:57:46 GMT

how to create transaction variant for a z -tcode.

Re: transaction variant

Former Member — Mon, 19 May 2008 10:03:12 GMT

Check out the below related thread

http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/frameset.htm

Regards,

Santosh

Re: transaction variant

Former Member — Mon, 19 May 2008 10:07:28 GMT

Hi,

steps to create the transaction varient are in the following link,

http://www.sapdb.info/wp-content/uploads/2008/05/transaction-variant-step-by-step-creations.pdf

Transaction Variants

Transaction variants simplify transaction flow by:

Inserting default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

Hiding individual menu functions

Hiding entire screens

Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

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.

Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

Re: transaction variant

Former Member — Mon, 19 May 2008 10:07:40 GMT

Hi,

Transaction Variants

Use the transaction SHD0 , this used in cases where you need to make your own variants to the standard TCODES, like hiding some input fields, hiding some screens, make input disabled, etc.

By using Transaction variants you can do all of them

SHD0 is the Tcode for creating Transaction Variants.

Procedure to create.

In SHD0 first screen:

you need to give Transaction as (lets take MM01) for that variant is (Say something ZMM01).

Means here you are creating transaction variant to activate/deactivate/make mandatory fileds in the screen those comes in MM01.

In SHD0, create the variant ( some name ZSM30), save it, then come back to original screen(SHD0)--~~GOTO~~> create varaint transaction. there u can click and give ur variant transaction name.

SHDO is the transaction code for creating transaction variant

Transaction Variants STep by STep

1. Enter tcode of which the screen you want to create the

variant (for example : crmd_bus2000115)

2. Enter Transaction Variant Name

3. Click Create button

4. Now, navigate through the screen to which screen

you want to have it on your trans. variant

(click OK/confirm on each popup screen)

5. Click Exit and Save on popup screen, if you want to

finish the screen variant.

6. Save your work

7. If you want to customize further (like hiding some

buttons/functions) then you can proceed by clicking

on CHANGE button (pencil icon)

8. Assign Tcode to this new Trans Variant.

9. Done

Transaction Variant

You can only create transaction variants for dialog transactions and reporting

transactions.Only "normal" screens, dialog boxes, and subscreens can be

included in the variant.

Screen Variants are automatically created anytime you create a

transaction variant.

Initial Screen

Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to the client-specific transaction variant maintenance transaction.

Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.

Creating the Transaction Variant

Choose Create to create a variant.

The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).

Here you can determine:

if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)

if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")

if field contents are saved (the "With contents" checkbox)

if the ready for input status of specific fields should be revoked (the "Output only" checkbox)

if specific fields should be hidden (the "Invisible" checkbox)

if specific fields should be mandatory the "Mandatory" checkbox)

You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).

Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).

Choose the function Continue to proceed. The following pushbuttons are available:

The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.

The Menu functions function displays an additional dialog box wher you can deactivate menu functions.

The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).

The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).

Enter a short text for your transaction variant here.

Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.

Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.

You can also branch to this list using the Change values function during the function selection process.

Deleting Preassigned Values

You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.

If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.

Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.

Reward useful answers.

Regards,

Raj.

Re: transaction variant

Former Member — Mon, 19 May 2008 10:20:25 GMT

Hi,

Check this.

Regards

Kiran Sure

topic Re: transaction variant in Application Development and Automation Discussions

transaction variant

Re: transaction variant

Re: transaction variant

Re: transaction variant

Re: transaction variant