Transaction variant issue

Hi All,
I have created a transaction variant for transaction ME21-Create Purchase order.
Now my requirement is to change the transaction text displaying on the screen…
i.e. to change the text Create Purchase Order: Initial Screen to “Create Local Order: Initial Screen”.
But this should not affect the standard transaction ME21...
Thanks & Regards
Shiva

Hi Raees,
From your post, it seems like no issue and cant make what's wrong?
But please check this link and verify you're not missing any step:
[http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
I hope this helps.
Regards
Raghu.

Similar Messages

  • Transaction variant issue (T-Code SHD0)

    Hi,
    I am trying to create a Transaction variant for T-Code SM30 for providing row level filter to a particular View.
    During recording when I select the radio button - "Enter Conditions" on the selection screen of sm30, it doesnt reflect in the recording. Also all the options corresponding to radio button are disabled. Let me know for further clarifications.
    Also please let me know if there is any other workaround for providing row filter to a table View.

    Hi,
    Even though question is already marked as answered, I think that Pince Kummar requirement was not fulfilled.
    Those are the steps that you should execute:
    1. Create a Selection Variant:
    In FBL1N transaction, enter your required field values, and click on the save icon. Maintain variant attributes as you need. Assign to your selection variant a name beginning with CUS&. With that prefix you specify that is a customer system variant.
    2. Assign the created selection variant as default for tcode FBL1N.
    Go to SE93 and change FBL1N, on "Start with variant" field select your created CUS& variant and save.
    At this time you can notice that FBL1N transaction always begin with your selection variant.
    3. If you also want to disable Dynamic selections function, you should create a Standard transaction variant.
    Go to SHD0, enter the transaction code name (FBL1N). In the Standard Variants tab enter a name and choose create function. Automatically FBL1N selection image will be showed, click back button to return. In the screen that now is showed, choose "Menu Functions" and enter Program "RSSYSTDB" and gui status "%_00" and click Menu Functions, then in the tree that come out, find and select Dyamic Selections function (%_00->Edit->DYNS), next click disable button and then continue button.
    Now you return to Transaction variants maintenance screen. Make sure that in deactive functions list, for Dynamic selections function is only active "For Transaction" check box. Now save and activate your transaction variant.

  • Transaction variant issue in mm02

    HI,
    We have created a transaction variant in mm02. that is we have limited some fields in mm02 to and created another tcode.
    But when we go from this tcode, the field restrictions and all are working properly. But say in the middle of tht transaction u give the back button and say not to save, it'll go back to the original mm02 screen rather thn the screen for the new tcode.
    How cn we change this??
    Thanks
    Keshi

    Assign the transaction variants to T.CODE: SE93
    Here create new "z" t.code and assign your transaction variants name .before that your transaction variants save into package not local objects.create package in se80.

  • Authorization issue on SHD0 transaction variant in R/3

    Hi,
    Can anyone help me on the below issue?
    Created a transaction variant ZME31K using SHD0 on R/3 system with the base transaction ME31K.
    And created a transaction ZME31K for the above transaction variant.
    Created one ID which has access only to transaction ZME31K.
    But when tried to create contract using ZME31K, it allows to create the contract, but ended up with message  "You are not authorized to use ME31K".
    Anyone faced similar issue before? how this can be resolved? As per the busniess requirement, they can provide access only to the transaction variant for the user and they will not be assigned to ME31K.
    -Thanks,

    > We are doing an Upgrade assessment wherein at R/3 side, the system is being upgraded from 4.6 to ECC 6.0.
    > I wanted to know the impact the Change in Transactions at R/3 side..  namely transactions..
    > AS02, CT02, F-02, F-41, F-49, FB01 would have on BW.
    What do you mean? I don't get your question. What impact should those transaction have on BI?
    Markus

  • Transaction variant for Goods Issue going back to MB1A transaction screen

    Hello,
    I have created a transaction variant ZMB1A for Goods issue.
    When the goods issue transaction completed by using ZMB1A system again going back to the initial screen of MB1A. (Since it is the base of MB1A)
    Here the issue is everytime user had to enter the ZMB1A transaction. (for example if the user wants to issue material for different plants).
    Please suggest any suitable method to avoid the above multiple t code execution.
    Regards
    Rifaie M

    Hi,
    In SHD0, do the complete processing of Transaction MB1A during creation of Transaction Variant "ZMB1A" till posting of the Material document.
    To create a new T-Code as ZMB1A, go to Transaction SE93 and here enter Transaction Code as ZMB1A and Click Create button. Now enter Short text of Transaction and select option "Transaction with Variant (Variant transaction)" and press enter.
    Here enter following;
    Transaction             MB1A
    Transaction variant     ZMB1A
    Activate "Cross-client"
    Select Professional User Transaction
    Activate SAP GUI for HTML
    Activate SAP GUI for Java
    Activate SAP GUI for Windows
    Now Click SAVE button.
    Now you can start using Transaction ZMB1A which will call Transaction Variant ZMB1A.

  • 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!

  • Transaction Variant thru SHD0 issue

    Hi,
    We have created a Transaction Variant for VL01N --> de-activate Post Goods Issue button thru tcode SHD0.
    Now issue is that it effect of other client also.
    Means we have 3 clients on same server. and ab above requires only on single client. But if also de-activate on others.
    How can I do the same for single client.
    Please guide.

    Even though user can able to do PGI thru VL01N tcode
    If your project have a Security team and they have done this, I don't think, it is possible.  If you have authorization to SUIM, execute it, click on Roles > By Authorization Object.  There check once again for that user whether they got the authorization.  If you don't have authorization to access SUIM, then execute UST12 table through whichh also you can check.
    G. Lakshmipathi

  • Issue in Transaction Variant creation

    Hi,
    We are trying to create a Transaction Variant for VA01 t-code so that we want to greyout the 'Payment terms' field in the sales order.
    when I test the screen variant it is working fine where as the same is not working when assigned it to the transaction variant ?
    any inputs ? idea ?
    Thanks in advance,
    Vasanth

    The solution is here :
    Screen variant for Create Sales order

  • Transaction variants

    Hi, I have one issue regarding transaction variants. I have created a transaction variant for a program (standard & customer developed) and want to assign it to a user in transaction SU01 - Parameter tab. What I don't know is what kind of Parameter ID to choose to get this work? I have tried to modify ITS service PZ03 (transaction PZ03) and tried to assign the transaction variant to special kind of users without luck.
    /Best Regards
    Patrick

    Hi Patrick,
    When you create a transaction variant, I assumed you created a Z transaction that points to PZ03 with a variant. Then in your user profile, you should have this transaction code included. Parameter id tab in SU01 is for the default values of a parameter id when a user logs in.

  • Transaction Variant: BBPSC02

    Hi Experts,
    I am facing a problem with the transaction variant which I have created for the standard transaction BBPSC02. Below are the steps which I have followed to create it in development system:
    In SHD0 Transaction, I have first created a variant group Z_CTLG_ACC_GP and saved it,
    As we know, the transaction variant name will be automatically judged by SAP, i.e. when I went to the transaction variant tab, automatically a name will be there, here it was Z_CTLG_ACC_GPBBPSC02 for me.
    Then I have clicked on the create button and as usual it gave me a popup message that the transaction variant Z_CTLG_ACC_GPBBPSC02 belongs to the variant group Z_CTLG_ACC_GP.
    I have clicked on continue, and then in the next set of screens, I have made some fields in the screen 0110 and 0150 invisible as per the requirement.
    Now In the last screen I have clicked on the button u2018Exit and Saveu2019 which took me to a screen where all the screen s are lined up, there I have given a description to the transaction variant u2018Restricted Access to SRM Catalogsu2019.
    Then saved it and went back to the main screen of SHD0.
    Now, I have created a variant transaction u2018ZSSRM_CATALOG_ACCESSu2019 and assigned the created transaction variant to it i.e. Z_CTLG_ACC_GPBBPSC02
    Now In the variant group tab, I have assigned a user u2018USER_85055u2019, who has only one transaction in his role i.e.  u2018ZSSRM_CATALOG_ACCESSu2019
    Now this user u2018USER_85055u2019 can see his changes successfully in the SRM link for the development system.
    But the customer came up with new requirement that the changes should also work for the normal user without affecting the standard one i.e. When the normal user goes to ZSSRM_CATALOG_ACCESS, he should see the respective changes, but when he uses the standard transaction i.e. BBPSC02, he should not get affected ( standard should not get changed).
    This particular requirement is working perfectly in SAP GUI for the development system. But when the normal user goes to this transaction ZSSRM_CATALO_ACCESS in SRM link, he is not able to see the changes.
    To overcome this I have tried to add even the normal user to this variant group Z_CTLG_ACC_GP, but it is reflecting the changes in standard also.
    Could anyone please help.
    Thank you very much in advance.
    Edited by: venkatesh333 on Apr 21, 2010 3:13 PM

    We have created a new service to resolve the issue.

  • VA01 Transaction variant Field Modification

    Hi All,
    I need to deactivate ( make input = 0 ) certain fields in VA01 txn which has a transaction / screen variant. Everything thing works fine but the problem is, the other fields which was deactivated (make input = 0 ) using transaction variant appears in the screen ? Can you people tell how to solve this issue ? The user wants the screen as per the transaction variant. I am using the exit "FORM FORM USEREXIT_FIELD_MODIFICATION ?
    Thanks.

    The scenario is such that when the sales order is created against the invoice, some fields in VA02 still can be modified. but the user dont want that to be happened beyond the certain date. But it could be mofied with in the certain date. Now the problem is when i modify the screen as per the requirement, the fields which are hided using transaction variant appears in the screen.  when i comment my code...
    the transaction variant works properly ( i.e the fields got hided ) my code would be like.
    Date logic....
    IF SCREEN-NAme = VBAK-ZTERM.
    input = 0.
    modify screen.
    endif.

  • Transaction Variant for BD87 ? possible

    Hi all,
    I have the requirement to get a user access to BD87 but only for specific message types and status.
    I created a selection screen variant with the correct values.
    Then I tried to create a transaction in SE80 for the report + selection screen variant, but it was not accepted.
    I also tried to create a transaction variant in SHD0 but I'm lost. I didn't get it managed.
    Does anybody of you know if in principle it should work with BD87 or do you have another solution to solve this "little" problem.
    Thank you very much in advance
    regards
    Hans

    Hi,
    I have this issue as well, and wonder how I can limit access to change the variant?
    What I have done:
    Created a selection screen variant for BD87, limiting all unnecessary fields. I can of course create ZBD87 with 'start with transaction', but that won't limit the user to change the selections/variant.
    Any idea on how I can do this if I can't hide the menu functions in SHD0?
    Thans in advance!

  • Problem during transport of transaction variant.

    Hi Experts,
    Can any one tell me, the creation of transaction variant is client specific or not????
    As because a new transaction variant created through transaction code 'SHD0' is not getting transported properly from one client to another client.
    Kindly suggest a solution.
    Thanks & regards,
    Rupam.

    Hi,
    You can make it client specific as well as transportable.
    When saving your transaction variant in SHD0, if you select Package as "$TMP" or press Local Object button, your variant is client specific.
    If you want to transport it to another client, get the relevant package number from your Technical person or BASIS person, Then enter that package when saving. You'll get a transport Request number after giving the relevant Package.
    Then you can transport without any issue
    Creating transaction Code for that variant
    When you are back on the Transaction Variant (SHD0) screen, press Shift+F6 or click the goto
    menu and press the create variant transaction button.
    Through this transaction SE93 will be executed. Enter the transaction name you want to create
    and any other required field and now press the save button.
    Tick u2013 Cross Client.
    EG:
    Transaction Code u2013 Z Transaction code that going to use in future
    Transaction u2013 Standard Transaction code
    Transaction Variant u2013 Variant that created.
    At the point of saving get the transport request.
    Best regards,
    Anupa

  • Save Transaction Variant

    I wanted to disable all the  fields in a standard transaction (fv50). I have created the screen variants using SHD0 and made all the fields to Output only. In the last step when I am trying to save the transaction variant, system is throwing an alert "Specify the Package or flag it as a local object"
    Can anyone guide me how to proceed further ??
    Thank you
    Ravi
    Mobile 9849393564

    Hi Ravi,
    Good!
    After creating the screen variant, we need to save under one package(developmet class) or as local object.
    while saving please give any of the above it will relosve u r issue.
    Thanks,
    Sunil

  • Transport transaction variant

    Hello,
    using SHD0, I created a standard transaction variant ZIP01 for transaction IP01.
    But how can I transport this variant to other systems?
    I tried with program RSTRANSP with following parameters:
    - Program Name: SAPLIWP3
    - Variant name: ZIP01
    But I get the following error message: "Function cannot be used for local/private objects"
    Message no. DB275
    Diagnosis
    Variants cannot be transported if the relevant program has only been defined as a local/private object (development class $TMP).
    System Response
    No transport request generated.
    I thougt I had attached my transaction variant and corresponding screen variants to a development package but the systems seems to tell it is not the case. How can I check it (I am just a functional consultant trying to learn more technical things, not an ABAPer, sorry)
    By the way, I am not even sure it is the right way to transport transaction variants. In other threads, program RSTRANSP was mentioned to transport selection and layout variants but can it be used to transport transaction variants/screen variants created with SHD0 too?
    Thanks in advance for your help.
    Regards.

    Thank you both for your answers, but unfortunately I am still facing the same issue.
    @Arseni: I checked as you mentioned and yes, the variant is well assigned to a package
    @sFayaz: In SE38, when entering the program SAPLIWP3, and asking to display variants, I get the message:
    "Program SAPLIWP3 has no selection screens
    Message no. DB244"
    Is a "transaction variant" the same as a "program variant"?
    Edited by: Laurent Delhaie on Nov 25, 2011 12:01 PM

Maybe you are looking for