Transaction varient and screen varient

Hi all ,
What is the use of screen varient and transaction varient in CRM and What is the difference between them ?

hi there
What you can do with a transaction variant
Insert default values into fields
Change the ready for input status for fields
Hide various screen elements, menu functions or entire screens
Adjust table control settings
Note:
Transaction variants can only be used with dialog transactions.
How to create a transaction variant
Transaction variants are created with transaction: SHD0
In the field Transaction on SHD0 enter the transactioncode for the screen you want tpo modify (E.g. VA03)
In the field Variant on SHD0 enter the name you want to give the transaction variant (E.g. ZVA03)
Press Create
Now the screen for the transaction is shown and you can enter default values in the fields of the screen
Press Enter. Now a screen that enbles you to make further customizing (Hide, Output only, Invisible, Mandatory) if the screen fields is shown.
After you have finished customizing the screen press Enter to go to the next screen or ave and exit to save the Transaction variant
To run the transaction varian, you must create a new Transaction code in SE93 that referes to the Transaction variant. Choose Transaction with variant as Start object.
Note:
The transaction variant can also be called from a program that imcludes a call to function module RS_HDSYS_CALL_TC_VARIANT
Screen variants
To create a screen variant, use transaction SHD0. Use menu Goto -> Screen variants
The process to create a screen variant is similar to creating a Transaction variant. The difference between the two types is that a Transaction variant covers the whole transaction and therefore can have more than 1 screen, while a screen variant only can have 1 screen.
best regards
ashish

Similar Messages

Transaction Variant and Screen Variant

Hi
I have created a transaction variant ZTX for transaction TX.
The First screen of transaction ZTX IS Screen 0100 for example.
The Screen variant is ZSVAR and only for the first screen of the transaction variant ZTX, which is created when creating the transaction variant.
Then, I activated the transaction variant to be a Standard Variant.
Now in my program, if I say,
1. Leave to screen 0100.
Then, it takes me to the initial screen of transaction ZTX but the effect of the transaction variant is not there.
But if i code it as
2. Leave to transaction TX.
I can see the effect of the transaction variant.
Why is this ?
More-over, I cannot code a " Leave to transaction" as I will lose a lot of history.
What could be the remedy ?
I am new to Transaction Variants and Screen Variants concepts.
Thanks in advance for your valuable inputs.
Kind Regards
Prasad

Hello Prasad,
Leave to transaction will be considered as a new dialog process, hence all memory will be cleared. Try look at the standard transaction TX whether it uses parameter ids on it screen fields. In your program, set these parameter ids with the last values you are working on, before you call "Leave to transaction".

Transaction and screen varients

hi gurus
need step by step scrren shots for transaction and screen varients
my id :[email protected]
points award is sure
kishor

Dear Rama,
http://help.sap.com/saphelp_webas620/helpdata/en/eb/5fab41d79b11d296190000e82de14a/content.htm
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components -> Application Personalization -> Tailoring of Application Transactions -> Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Hope this will help.
Regards,
Naveen.

Creation menu item using transaction varient or screen varient

hi,
Can we create pushbutton or menu item in standard program using screen varient or transaction varient.

No , u cannt . But u can do it by changing its PF-STATUS that to by using user exits.
Regards
Prabhu

User specific transaction varient

Dear all,
I am having a requirement, for the tcode J1IH the posting date should be made as display field for all users except for one specific user.
1) For the above requirement i have kept 2 transaction varient.
2) One varient is used to make posing date as non editable for all users.
3) One more varient is used to make the posting date editable for one user. I have assigned that user to group name.
I do not how to activate this varients, since for all users except that one user the first varient should be active, for the specific user the second varient should be active. Kindly guide me to proceed further.

Good point. I think if you use an exit you can vary the call depending on User/User Group. However, that requires an ABAPer.
To do it yourself you could just create a copy of your transaction.
Assign the original transaction to the majority but not the single User. Assign the copy to the single User and apply a screen variant.
Regards,
Nick
Edit > ABAPer could do via call to function module RS_HDSYS_SET_SC_VARIANT
Edited by: Nick Whitehurst on Apr 1, 2010 10:59 AM

How can i assign the Transaction varient to the user in 4.6C version

How can i assign the Transaction varients n Screen Varients to the users in 4.6C version.
Actually Iam using T-code SHD0 for hiding the field in VA11 transaction. In this iam created one transaction varient n one Screen varient.iam not able to activate that screen varient and iwant to assing to perticular users. But i have a option in 4.7 above version my client is using 4.6C version. Please give me the solution as need full.

Hi,
Use the PPM toolkit class CL_CRM_PPM_UM_TOOLKIT. You can use the method You can use the method GET_ASSIGNMENTS_OF_USER which returns positions held by an user(user name). You may also find the method GET_POSITION_OF_USER useful. It accepts username and the organization ID and will return the positions held by the user under that organization.
This class always uses the current plan (01). If you want otherwise, you can use the FM RH_STRUC_GET. As to how this FM should be used, look inside the above said methods.
Regards,
Arun Prakash
Edited by: Arun Prakash Karuppanan on May 11, 2010 11:40 AM

Creation of transaction varient

hi,
My requirement is creation of transaction varient.
already they have created transaction varient " ZBP"for transaction "BP".
they are asking one more transaction varient for transaction "BP" with sliet different.
my question was can take the copy of of old one and can make the changes as per the requirementment?
how the new varient linked with transaction?
Could you please provide me required steps.
Thanks

hi
refer these two links, it would answer your questions.
transaction variant
Transaction variant?
Regards
Sajid

CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .

Hi all,
i hope there is someone that can help me.
My problem is: in an ABAP custom report in a FORM user-command my code is
CASE ls_selfield-sel_tab_field.
    WHEN 'ITAB-BELNR'.
      IF NOT ls_selfield-value IS INITIAL.
        SET PARAMETER ID 'RBN' FIELD ls_selfield-value.
        CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .
ENDCASE.
When i click on output field of my report, not skip first screen but only call MIR6!!!
How can i solve this problem?
Regards.

Hi,
First of all Please don't use all Caps for Subject Line
Test Following Sample Code it will solve out your problem,
DATA: it_bdcdata TYPE TABLE OF bdcdata,
      wa_it_bdcdata LIKE LINE OF it_bdcdata,
      belnr(10).
belnr = '100'. " Give Document Number here
DATA opt TYPE ctu_params.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-program = 'SAPMM08N'.
wa_it_bdcdata-dynpro   = '100'.
wa_it_bdcdata-dynbegin = 'X'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_CURSOR'.
wa_it_bdcdata-fval = 'SO_BELNR-LOW'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'SO_BELNR-LOW'.
wa_it_bdcdata-fval = BELNR.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_OKCODE'.
wa_it_bdcdata-fval = '=CRET'.
APPEND wa_it_bdcdata TO it_bdcdata.
opt-dismode = 'E'.
CALL TRANSACTION 'MIR6' USING it_bdcdata OPTIONS FROM opt.
Please Reply if any Issue,
Best Regards,
Faisal

Call transaction 'LS33' and skip first screen.

This doesn't work:
set parameter id 'LEN' field '04018091'.
call transaction 'LS33' and skip first screen.
I've found this:
<a href="https://www.sdn.sap.com/irj/sdn/message?messageID=3715690">https://www.sdn.sap.com/irj/sdn/message?messageID=3715690</a>
but I'm not sure about the exact meaning (wouldn't know where to put the *)
nor even about if it applies.
Thanks in advance.

Sorry, I mistook this forum for that of ABAP General.
Anyway, the answer is in
Call transaction 'LS33' and skip first screen.

CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.

Hi,
i'm using this in an report.
SET PARAMETER ID 'BES' FIELD WA_ITAB-EBELN.
SET PARAMETER ID 'BSP' FIELD WA_ITAB-EBELP.
CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
It works OK.
Is there any parameter ID to go in a sprecial part of an PO, for example
direct to materialdata or konditions?.
thanks.
Regards, Dieter

Hi,
I think u can do that by using BDC as used in this code please refer to this code.
FORM get_user_command USING cr_ucomm     LIKE sy-ucomm      "#EC *
                            cr_selfield TYPE slis_selfield.
CLEAR wa_final.
DATA BEGIN OF bdcdata OCCURS 10.
          INCLUDE STRUCTURE bdcdata.
DATA END OF bdcdata.
CASE cr_ucomm.
    WHEN '&IC1'.
      READ TABLE it_final INTO wa_final
               INDEX cr_selfield-tabindex.
      IF cr_selfield-fieldname = 'MATNR'.
        IF sy-subrc IS INITIAL.
          SET PARAMETER ID 'MXX' FIELD 'E'.
          SET PARAMETER ID 'MAT' FIELD wa_final-matnr.
          SET PARAMETER ID 'WRK' FIELD wa_final-werks.
          CALL TRANSACTION 'MM03' AND SKIP FIRST SCREEN.
        ENDIF.
      ELSEIF cr_selfield-fieldname = 'LIFNR'.
        IF sy-subrc IS INITIAL.
          CLEAR bdcdata.
          bdcdata-program = 'SAPMF02K'.
          bdcdata-dynpro   = '0101'.
          bdcdata-dynbegin = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-LIFNR'.
          bdcdata-fval     = wa_final-lifnr.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-EKORG '.
          bdcdata-fval     = wa_final-ekorg.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'RF02K-D0310'.
          bdcdata-fval     = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'WRF02K-D0320'.
          bdcdata-fval     = 'X'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-fnam     = 'BDC_OKCODE'.
          bdcdata-fval     = '/00'.
          APPEND bdcdata.
          CLEAR bdcdata.
          bdcdata-program = 'SAPMF02K'.
          bdcdata-dynpro   = '0110'.
          bdcdata-dynbegin = 'X'.
          APPEND bdcdata.
          CALL TRANSACTION 'XK03' USING bdcdata MODE 'E'.
        ENDIF.
      ENDIF.
ENDCASE.
ENDFORM. " get_user_command
regards,
sudha

CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN?

Hi, Gurus:
In my program, after I call 'CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.'    in the va02, user maybe do some change and save
then I want to get those change as the dollowing:
    select single uvall into c_complete_flag from vbuk
     where vbeln = lv_vbeln.
why I can't get the latest change.
Thanks,

VA02 usese the asynchronus update mehtod so, it gives you the message like "Order 1111 was saved" but the database update is still going on.
So, you need to wait for some time before facthing the data from the database.
You can use like:
WAIT UP TO 10 SECONDS.
But this statement will force you to wait for atleast 10 seconds before doing any thing.
Regards,
Naimesh Patel

How to transport a transaction variant and her related screen variant?

Hello to every SDN member,
I am looking to transport a transaction variant and the related screen variants.
I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
Can you please give me the solution to transport the transaction variant and the screen variant?
Thank you very much in advance.
Best regards,
Matthieu Chérier

Hi,
You can transport a variant by :
1. Running the program RSTRANSP. Mention your program and variant name there.
2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
3.Go to Se38 --> Input report name --> Select Variants
On the screen --> Go to Utilities -> Select transport request
--> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
Regards.

Create transaction and screen variants

Hello
I want to create transaction variant for VA01 and MM01 in order to simplify the data entry. I know SAP has SHD0 as a tool and Synactive has GuiXT to make all these changes. But I wonder what are the differences between these 2 tools.
Please let me know,
Thanks,
George

Dear Mr.George,
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.
If useful reward points.
Regards
Mangal

Transaction varients

Hi Experts,
I have created transaction variant via shd0 for MM02 controlling of some of fields in MRP screens(mrp1,mrp2,mrp3,mrp4), the variant is working fine for 1st material, from second material it is showing all screen of material, I mean, the variant in not working.
Please let me know how to control this transaction variant for all the materials.
Please help in this regard.
Regards
Rams

Go to transaction SHD0.
Enter the transaction code MM01. Now click on button CREATE.
Following information message would appear:
Click Enter to proceed.
Now the MM01 transaction would appear.
Select the required Industry sector and Material Type and press ENTER. Following popup would appear:
Now make the modifications as shown below:
Click on Exit and Save.
Following popup would appear:
Click Enter to proceed. Following screen would appear:
Save your entries and go back to the main screen.
Now enter the transaction variant name and click on Change button as shown below:
Now click on Insert Row.
Enter the name of the screen variant created earlier or use F4 help to select the value:
Now click on Goto à Create Variant Transaction
Enter the values as shown above. Click on Enter. The following SE93 transaction would appear:
The name of the Transaction Variant is automatically proposed. Save your entries.
Now go to Transaction ZMM01 and check your transaction variant:
You can observe that the field Industry sector and Material type default to the value we have given earlier and are output enabled only.
Regards.
swami.

There are two transactions ZJPVCS303 and ZJPVCS303_US for one single Report

When run as a batch program, (currently this is the case), or withT-Code ZJPVCS303 the selection screen is unchanged (except for additional sales area above)
- When run as T-Code ZJPVCS303_UL (UL stands for Upload) the selection screen is changed. The unix file option is no longer available, and the user is able to upload a local file (in the same format as the current unix file, but tab delimited) to the program for processing.
Requirements:
There are two transactions ZJPVCS303 and ZJPVCS303_US for one single Report.
->When ZJPVCS303 Transaction is executed, the file is uploaded from the Application
server to SAP R/3. The selection screen parameters would be:
Logical Filename:
Sales Organization:
Distribution Channel:
Division:
->When ZJPVCS303_US Transaction is executed, the file is uploaded from the Presentation Server
to SAP R/3. When this transaction is executed, it should not have the 'Logical
Filename' parameter anymore on the selection-screen. Instead it should only have
Local File name on the presentation server:
Sales Organization:
Distribution Channel:
Division:
    The same thing is applicable for the other transaction ZJPVCS303. When transaction ZJPVCS303
is executed, it should not have the 'Local Filename' parameter anymore on the selection-screen. Instead it should only have
Logical Filename:
Sales Organization:
Distribution Channel:
Division:
So how should I make these parameters invisible depending on the transaction codes execution.
I have an idea of using MODIF ID, LOOPING AT SCREEN...MODIFY SCREEN.
I have an idea of using SY-TCODE.
EX:
AT SELECTION-SCREEN OUTPUT.
IF SY-TCODE = 'ZJPVCS303'.
LOOP AT SCREEN.
IF SCREEN-GROUPID = 'GRP'.
   SCREEN-INPUT   = 0.
   SCREEN-INVISIBLE = 1.
   MODIFY SCREEN.
ENDIF.
ENDLOOP.
ELSEIF SY-TCODE = 'ZJPVCS303_US'.
LOOP AT SCREEN.
IF .....
ENDLOOP.
ENDIF.
ENDIF.
But I am not able to get the output which I require. Please help me out.

Hello Rani
Basically the transaction determines whether upload starts from application server (AS) or presentation server (PC). Thus, you will have the following parameter:
PARAMETERS:
p_as_fil          TYPE filename   MODIF ID unx, " e.g. Unix server
p_pc_fil          TYPE filename   MODIF ID wnd. " e.g. Windows PC
AT SELECTION-SCREEN OUTPUT.
CASE syst-tcode.
*   transaction(s) for upload from server (AS)
    WHEN 'ZJPVCS303.
      LOOP AT screen.
        IF ( screen-group1 = 'UNX' ).
          screen-input = 0.
          screen-invisible = 1.
          MODIFY screen.
        ENDIF.
      ENDLOOP.
*   transaction(s) for upload from local PC (PC)
    WHEN 'ZJPVCS303_US.
      LOOP AT screen.
        IF ( screen-group1 = 'WND' ).
          screen-input = 0.
          screen-invisible = 1.
          MODIFY screen.
        ENDIF.
      ENDLOOP.
   WHEN others.
   ENDCASE.
Regards
Uwe

Transaction varient and screen varient

Similar Messages

Maybe you are looking for