Transaction variant Tcode called in ZPROGRAM

Hi Folks,
I have created transaction variant for t code MM01.
And created a transaction code for this transaction variant using SE93.
ZMM01_MAT is transaction variant t code.
Now I am trying to call this transaction variant t code(ZMM01_MAT) from other program to fill the next internal material number and pass it to ZMM01_MAT(passing material no from program to screen).
When I select a select views and click on “sales:sale org. data1” view, it is not prompting the screen to enter plant/Sales org/Distribution channel values (it will prompt screen in MM01 and ZMM01_MAT transaction codes).
Below is the coded in ZPROGRAM where ZMM01_MAT is calling
SET PARAMETER ID 'MXX' FIELD 'X'.
SET PARAMETER ID 'MAT' FIELD lv_matnr.
CALL TRANSACTION 'ZMM01_MAT'.
please help us on this.
Sri

Hi,
I don't know if I understand your requirement.
If you want to add new variant TCODe like MIGO_TR and assign Accounting document, I would follow this way:
1. try to add entry to table T158 (in SE16)
2. use related entry (for existing TCode) as a reference for fields entry.
3. save and test if it works
hope it helps.
regards,
wojciech

Similar Messages

Standard transaction variant ZMSC2 for transaction MSC2

Hi
I have created a standard transaction variant ZMSC2 for transaction MSC2. When i do the recording for MSC2... I dont see the transaction variant being called..
Please suggest

hi
any suggetions

Transaction variant SYST-TCODE

Dear all,
I created transaction variant ZVA02 as copy of VA02. If I start transaction ZVA02 the field SYST-TCODE is filled with VA02. Where can I see that the transaction was started via ZVA02. Is this information available in the order entry process?
Thanks.
Kind regards
Frank

You can use the method GET_CURRENT_TRANSACTION of class CL_DYNPRO.
An excerpt from the SAP documentation:
Alternatively, the method GET_CURRENT_TRANSACTION of the class CL_DYNPRO can be used to obtain the transaction code of the current transaction. This method returns the transaction code during a parameter transaction or variant transaction instead of the transaction code of the implicitly called dialog transaction.
Source: [http://help.sap.com/abapdocu_70/en/ABAPLEAVE_TO_TRANSACTION.htm|http://help.sap.com/abapdocu_70/en/ABAPLEAVE_TO_TRANSACTION.htm]
Hope this helps.
BR,
Suhas

Call transaction variant - crmd_order

Hi,
i have created a new transaction variant for cmrd_order. I'm trying to call the new tcode (zcrmd_order) in the abap code by passing the order number using call transaction.
i have used the call transaction ..with bdcdata mode 'E' and im having problems. it works fine ...but now and then it displays the pop up box and couldnt figure out why.
is there a better way of calling this transaction variant.
Thanks,
kris.

Hi Sandra,
i'm using the following statement
Call transaction 'ZCRMD_ORDER' using t_bdcdata options from T_opt .
Some users are getting the pop-up box while for others its working fine. it works fine when the call transaction statement is being called for the first time. But when its called for the second time, this pop-up box appears.
Not sure why this is happening.
I have recorded the screens and passed those to bdcdata tab and didn't use skip first screen.
Let me know where i'm going wrong.
Thanks,
kris.

Problems with SKIP FIRST Screen when calling a transaction variant

Hi,
I have a transaction variant of VA02 that suppresses the display of the pricing button on the conditions screen. I have created a variant transaction for called ZA02 which calls this variant of VA02.
In my program I have coded the following :-
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'ZA02' AND SKIP FIRST SCREEN.
I would have expected the program to display the second screen of VA02 but it displays the first screen and when I hit return key the second screen is then displayed.
I don't think I need VPO setting but when I code
      SET PARAMETER ID 'AUN' FIELD VBELN.
      SET PARAMETER ID 'VPO' FIELD POSNR.
      CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
VA02's second screen is displayed
Any help as to how to Skip this first screen with ZA02 would be greatly appreciated
Thanks
Rous

Yes you are right Reg thanks for that.
But it appears that VA02 doesn't require it setting anyway. I changed the PID to APO and indeed I've even commented the line out, but my program goes to the second screen when calling VA02 but stays on the first screen when calling ZA02 .

Transaction Variant for tcode SP01

Hi All,
I am trying to create the transaction variant for the tcode SP01 by using tcode SHD0.
Steps I followed are:-
1. Create tcode ZSP01
2. In SHD0, tcode as ZSP01 and hit the Create
3. Control goes to Screen SP01 inital selection screen
I need to change 'created by' as display only and cannot get the screen attributes.
Any help will be greatly appreciated.
Regards,
Azhar

Thanks for the quick reply.
I found that SP01 is a module pool program with screen 2000 then I should be able to create the transaction variant.
I tried creating the tcode with your suggested authorization object getting warning message 'Check object has been maintained(Press enter to reset)' and when I press enter the auth object field will get reset.
Thanks for your quick response and suggestions.

Call transaction variant from IW51

hi ,
i have created a transaction variant for va01.
i want to call this transaction only when user creates sales order
from IW51(service notification) .i dont know how to call transaction variant from iw51.
i would appreciate your help on this.
thanks,
yoga

Hi,
You may refer this
Passing Variant's value to a transaction iview
Thanks
Prashant

Transaction variant from TCODE ME51n issue

I am created Transaction variant Against transaction ME51N and ME52n ( two transaction variant ) we donu2019t want to give transaction me51n and me52n to users.
But the problem is that when I revoke the transaction Me51n and me52n from users and give them to transaction variant transactions YME51N and YME52N when the user run that transaction error occur that missing authorization object S_TCODE and value ME51N same in run in transaction YME52n the required transaction is me52n. we donu2019t want to give both transactions to users please help me regarding this issue
thanks

Check whether you are using it right.following extract from SAP help apply.
Transaction type: Variant transaction
In the SAP Reference IMG, under "Basis Components" -> "Application Personalizaion" -> "Tailoring of Application Transactions", you can define transaction variants. These allow you to preassign values to fields within a transaction, define field attributes, or hide entire screens.
To run a transaction variant, you define a variant transaction. On the next screen, enter the name of the transaction and the name of the variant.
If above does not work there is a brute-force alternative- a little abap can be fired whenever someone executes me52n or yme52n to go after sy-uname and thereby call yme52n or me52n as need be!

Call SAP Transaction Variant from Iview

Hello,
I know we can pass parameters into a SAP transaction via the 'Application Parameters', but this does not always work especially for complicated selection screen options.
Can the actual transaction variant ID be passed instead?
Regards
Mr.T

Hi,
You may refer this
Passing Variant's value to a transaction iview
Thanks
Prashant

Problem with transaction variant

Hi Gurus,
I want to create transaction variant for XD01 transaction and make district field mandatory.
I have done it using transaction SHD0 and its showing effects when i test it from SHD0.
But I cant see its effect in actual transaction XD01.
Please guide.
Thanks in advance,
Supriya.

Hi,
The transaction variant created by SHD0 when activated will change the display of tcode SM37, irrespective of whether it is called directly or from a Z program. If you are calling SM37 from Z program, try
SUBMIT SAPLBTCH VIA SELECTION-SCREEN WITH SELECTION-TABLE rspar_tab AND RETURN.

Transaction Variant for VA41

Hello,
I have a requirement in which two fields in the Billing tab of the document header in the VA41 transaction to be grayed out or input disabled. Tried out the transaction variants option, but seems like its not working. When I test the variant from SHD0, it is working fine. But when the standard tcode is called, the changes are not in effect. Tried out the option of creating variant transaction as well but in vain. The same problem exists.
Am I missing out something while linking the variant to the standard transaction?
Thanks,
Samson

Hi,
Creating a transaction variant and assiging the screen variant that you have created should fulfill your requirement check teh below link:
LINK[Maintain Trans Variants:|http://help.sap.com/saphelp_nw04s/helpdata/EN/7d/f63a0a015111d396480000e82de14a/content.htm]
in order to create a transaction variant after you ahve created your screen variant is like below:
1. In transaction SHD0 GOTO>Create Variant Transaction
2. Enter the transaction you want to create then maintain the values in the next screen.
Regards,
Himanshu

Syst variable for transaction variant?

Hi,
How to identify current transaction code with variant. We can't use sy-tcode as it shows orginal transaction code. Sy-slset is also empty allways?
Thanks
Shekar

hi Reddy ,
check the Documentation of SHD0.Its nothing but modifications of Screen fields.
Regards
Prabhu
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
Prabhu
PS : Customer is First Points next

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

How to create Transaction Variant

Hi all,
I have a requirement like this
I need to create a transaction variant for the table CEPCT, for the transaction SE16 and want to disable or invisible CREATE and CHANGE options in that
Can any one help me out in this requirement
Regards
Srinivas

Hi,
Recording a Transaction Variant
Transactions variant are recorded through transaction SHD0.
   1. Enter the transaction code you want to record u2013 here BP, and press enter
   2. Enter a name for your transaction variant u2013 here Z_BP_NO_PERSON. Please notice that the naming convention for transaction variant requires that it starts with Z or Y.
   3. Push Create
You have now called transaction BP in recording mode.
   1. When you push the exit button you will get the following popup
   2. Enter a name for the screen variant u2013 e.g. Z_BP_NO_PERSON,
   3. Press the deactivate menu function, and you get the following popup.
In this Popup you can deactivate menu functions.
   1. Open the Menu Bar à Business Partner à Create
Position the cursor on u201CSCREEN_1000_CRE_PERS Personu201D
   2. And push the deactivate button.
   3. Push enter
   4. And u201CExit and Saveu201D
   5..Save the Transaction Variant.
Thanks,
NNR.

How to create Transaction Variant for T code F-30

Hi
I want to create a Transaction variant for T code F-30, so that user can't change the currency field and put any value in rate. Currency should be always in USD.
Any input will be heighly appriciated.
Regards
Shiv

Hi,
In that case you can use transaction SHD0 to create a transaction variant for F-30 with its screen variant for screen# 122. And you also want to creat a so called Variant Transaction Z-something for F-30 using the mentioned transaction variant. You restrict users to use that Z-something. For other unrestricted process, the system will still cal F-30. Here is the documentation:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/67/232037ebf1cc09e10000009b38f889/content.htm
Regards

Transaction variant Tcode called in ZPROGRAM

Similar Messages

Maybe you are looking for