Transaction variant not recognized

I have created a transaction Variant (called ZPRAP_VAR) for transaction PRAP (approval of trips in FI-TV). I have also activated it to be the standard variant.
I have created a variant transaction (called ZPRAP) for the PRAP transaction with variant ZPRAP_VAR. When I call the variant transaction ZPRAP from Workbench, the transaction variant ZPRAP_VAR is not being called automatically.
I have to pick the tx variant from the "Get Variant" menu explicitely. Any idea why?

Hi,
Look at the below link
http://www.sap-basis-abap.com/sapbs010.htm
You need to give the Z transaction code for the transaction variants, and select the appropriate checkboxes then Save and activate it,
Regards
Sudheer

Similar Messages

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

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.

SHD0-Transaction Variant not correctly hiding screens from tabstrip control

Hello All,
I have created a transaction variant for transaction PPDPIM. It is my intention to hide all tabs on the second screen of the transaction except for one. This is working. However, I find that my results are as follows:
1. The tab I have left as visible is, in fact, visible. All others are invisible. This is good and what I want.
2. For the one visible tab, the subscreen contains the structure/information found on the DEFAULT tab (which is not the same as the chosen visible tab). This is bad.
It would seem that somewhere in the application the default tab is being set and somehow overriding the transaction variant. Has anyone found a solution to this type of problem?
Thank you.

I have used the "Invisible" checkbox on the subscreen screen variant as the only configuration. I marked this check box for 5 of the 6 tabs with outcome as outlined in my first message.
If I include the "default" screen (giving me two visible screens) then both screens display properly. This does not seem consistent.
Has anyone had a similar problem who can give me some constructive suggestions?
Thanks

Transaction variant not assigned

Hello Sir,
While I am posting the payment/receipt document in FBCJ (Cash Journal) I have got the error as - No accounting transaction variant assigned to FBCJ/K3. Where K3 is the document type.
BSR

hi BSR,
Pls check in OBA7 whether u have created the Document type and it is assigned in Tcode FBCJC1. If it is not assigned pls assign to it......
if it is usefull..assign me the points...
ranjit

Screen variant not working when assigned to transaction variant in SHd0

Dear All,
User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
Thanks in advance
Komal

Hi,
Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
Once done and saved, you can see all the screens variants in the transaction variant.
Use the Change WITH PROCESSING OPTION.
Hope this solves your problem
Regards
Shiva

Two transaction variant do not working for a user

Hi Gurus
I have created two Z t code and made transaction variant through T Code SHD0 and assigned these two ZTcode to a user. now when a user is running the Ztcode screen variant is active on only one. when i assign second one to the user again than screen variant of first ZT code do not work.
can any one tell me why system is doing so.
Regards
Shiv

Hi, I have the same situation. Can you please help how your case got solved ?
Basically I have created two transaction variants- one for XD02, the other for XD03. When I am trying to assign a user to both these transaction variants ( using SET PROPOSAL), only one is getting assigned, other is getting deactivated. Please help.

Transaction variant to disallow change in FB02 not working for FBL5N / FB09

Hi SAPtechies,
I have created a transaction variant to disallow change in all fields other than Text (BSEG-SGTXT), and activated it for standard transaction FB02.
This works well when FI document is changed via transaction FB02, but fails when the same document is changed via FBL5N / FB09.
The screen is same for FB02 & FBL5N:
Program (screen)     SAPMF05L
Screen number        301
Program (GUI)        SAPMF05L
I have already checked for enhancement in PBO INCLUDE MF05LO00, but there was no success.
Can anyone suggest me another methadology to greyout or make FB02 fields uneditable, with same functionality also working for FBL5N/FB09?

Hi ,
I could achieve a way to disallow editing in FB02 item level fields using substitution & custom exit.
Additional requirement was that I want to assign authorization for particular users who can change all fields.
Any suggestions on it?
Our Basis team has created new role & assigned this role for FB02.
But this role has got many technical authorization objects.
Below check is not working:
AUTHORITY-CHECK OBJECT 'S_TCODE'
           ID 'TCD' FIELD sy-tcode.
Thanks...Tanaya

Transaction variant for VA02 is not working for few fields

Hi All,
I have created a transaction variant for VA02. Made the necessary code changes for populating the variant name in MV45AFZZ. It is working fine for all the screens and all the fields except for second screen of VA02.
First screen - Enter sales order number.
Second screen - Overview screen.
In second screen, I have disabled all the screen fields. When I run the variant, all fields are disabled except sold-to party, ship-to party and create sold to party ICON. All these fields belongs to screen 4701.
In the transaction variant I can see that these fields screen attributes set to output only. I don't see anything different for these fields compared to other fields.
First I thought it is because of mandatory fields. But some other mandatory fields are disabled after my changes. Why is this happening only for these 3 fields (Only for screen 4701 I can say).
Surprisingly, if I do any action like enter/select other tab, these fields are getting disabled.
Your inputs on this are highly appriciated.
Thanks,
Vinod.
Edited by: Vinod Kumar Vemuru on Dec 31, 2009 10:01 AM

Thanks, happy to see the reply.
But I have given the correct names as suggested by you.
I have also created a Transaction ZVA02 as i dont want this variant to be applied on standard VA02.
It is working on first screen but not on subsequent screens. Am i missing something, some link or activation?
Transaction Code VA02                  Change Sales Order
Transaction Variant ZTRN_VA02                       testing
ZTRN_VA02_0102                                        SAPMV45A     102
ZTRN_VA02_4001                                        SAPMV45A     4001
ZTRN_VA02_4021                                        SAPMV45A     4021
ZTRN_VA02_4050                                        SAPMV45A     4050
ZTRN_VA02_4401                                        SAPMV45A     4401
ZTRN_VA02_4701                                        SAPMV45A     4701
ZTRN_VA02_4900                                        SAPMV45A     4900
when I run this the first screen is applied correctly but what happens next.

SHD0 and VA01 transaction variant: Changes not showing in Test mode

Hi,
I am trying to create a transaction variant using SHD0 for VA01 and VA02 that will grey out the PLTYP field in screens 4301 and 4900.
Everytime I go through the process and exit and save it looks fine, but when I test the variant, the fields are still editable, even though my variant shows them listed as Output Only checked off for the aforementioned screens
I am using the following:
T_Code for variant: VA01
Variant: copy of BUS2032 renamed Z_BUS2032_KPW.
screens to be affected : 4301 and 4900.
I do not want to override the default variant. I am currently in R/3 4.6c.
Any help other than links to the SAP help website (which I have exhausted) would be greatly appreciated.
Thanks,
Kevin Webb
www.innovapost.com

Hello Sai P,
HELP!
I have a similar situation: VA01 running standard and ZVA01, with a hidden field, once I assigned NO_VARIANT to the Order type ZVPV, it is working as desired. However, one strange thing is happening... when I enter ZVA01 and assign the order type ZVPV (which has NO_VARIANT at VOV8) I enter and the field is hidden this all good, then I go back to the screen were the order type is assigned and then I choose another order type ZTA (which has variant in VOV8 in blank) and the hidden field shows, all good as well. However, when I go back again to the order type screen (without going back to the menu screen) and choose again ZVPV and enter the field is showing. Any idea?
Regards.

Transaction Variant do not commit skip first screen

When I am calling to transaction variant its open
bu not commit the skip first screen .
Does someone know how can i fix it ?

Hi Kobi ,
as per my knowledge , there is no such command in SAP to skip first screen for transaction variants.Transaction variant is nothing but a transaction with some modifications.
but what u are talking abt is calling transaction , so this u have to call like this --->

call transaction 'MM03' and skip first screen.

Regards
Prabhu

TRANSACTION VARIANT

Dear All,
I am facing a problem while doing the transaction variant. It is as follows -
With the T.Code SHD0, i started creating a transaction variant and named as ZMM01 for the transaction MM01.
After clicking the create(F5), it went to the MM01 transaction for recording. Here i wanted to give some default inputs in the fields Industry sector and Material type, i gave my default values and pressed enter, then "Confirm screen entries" screen popped up. Here i selected(marked) required check boxes and clicked "Exit and Save". It went to another screen where i gave "Screen variant short description" and when i clicked on save, "Create Object Directory Entry" screen popped up.
What exactly should i do now?
When i tried to save by clicking on save button, system is giving me a message "Specify the package or flag it as a local object"
"Message no is TR742".
BUT.....
When i clicked the "Local Object" tab which is next to "Save" button, system is asking me to Assign a package" and in the package field the system is giving the value "$TMP" by default and when i tried to save it OR click "Local object" again, system is giving me an error message "Test objects cannot be created in foreign namespaces", Message no. TO131.
Pl guide me what exactly i have to do at this stage( How/Procedure to save).
Thanks & Regards,

Hi ,
Ensure that all the variants you have created start with Z like screen variant , transaction variant .
The system throws this message when you use other name space which is not allowed .
Regards,
Hari.

Transaktion variant not working

Hi experts,
I am facing a problem with a transaction variant.
I am creating a transaction variant in transaction SHD0. But can't get it to work when I afterwards is calling the transaction BBPSC02?
Step By Step:
1. Go into transaction SHD0.
2. In the field transaction code I write BBPSC02.
3. On the 'Tab' Transaction variants I write the name for the variant.
4. Go into the variant a make the field DELIV_DATE for screen 120 invisible.
5. Activate the variant.
6 Call the transaction BBPSC02 in the Gui and the Web. The field DELIV_DATE is NOT invisible??
What am I doing wrong??
Best regards Kim

Hi
you can refer this as Dave check list.
Re: To make the field for Display only on the Shopping Cart Portal
and you can cross verify from step 9.
regards
Muthu

Screen Variant Not working

Hi,
I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
It's getting called while i checked by debugging .
But its not working in ITS Template & in transaction also .
In SAPgui it's not working .
Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
Thanks,
SS

Hi
This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.
Please read the following documentation to get the clear difference
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).
Screen variants
Screen variants allow you to simplify screen editing 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
A screen variant contains field values and attributes for exactly one screen. A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
For more information, see: Calling Screen Variants
A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
Hope this will help.
Please reward suitable points.
Regards
- Atul

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 not recognized

Similar Messages

Maybe you are looking for