Standard SO type overwrites transaction variant

Hi all,
We have configured transaction variant for VA01 for certain sales order types.
It is working fine for those SO types.
The problem is when we use any other SO type where the transaction variant is not used then for the next entry of SO type (with transaction variant) the fields which are supressed are again visible in VA01.
For example we have two order type SO01- With transaction variant & SO02- With out transaction variant.
If for the first time in VA01 if create sales order with SO1 then it transaction variant works fine.
In the second case if we create SO with tyep SO02 then when it comes back to initial screen of VA01 & give entry for SO01 then all the fields which are supressed are visible again.
To avoid this we need to re exceute VA01 which is not advisible.
Guide us to overcome this.
Mimiri

Awaiting your valuable replies
Mimiri

Similar Messages

Overwrite Standard Movement types with Z movement types in MI10

Dear All,
We have a requirement where we need to replace standard movement types 701 and 702 with Z movement types in transaction MI10. Would there be any exit or BADI in MI10 which would serve this purpose?
We also tried cloning the transaction MI10 but some checks on the TCODE is giving an issue.
Any one come across a similiar requirement, kindly help.
Thank you.
Johnson
Edited by: Johnson Ittyerah on Dec 19, 2007 2:20 PM

following badi may help to change the movement types:
MB_DOCUMENT_BADI
Regards,
Gopi ,
reward points if helpfull.

Assign transaction variant to standard transaction.

Hi All,
I want to alter the column nos. in table control for transaction VA41 / VA42.
I created transaction variant ZVA41 using tcode SHD0. I have created new tcode ZVA41_1 using SE93, option 4 - Transaction with variant. I have used transaction - VA41 and transaction variant ZVA41_1 in SE93.
When i am testing this new Tcode ZVA41_1 from SE93 only, its working fine. but when i am executing tcode ZVA41_1 its not displaying screen as per new variant ZVA41. Its displaying standar screen of VA41. Not getting what else i need to do? I also tried to assign this variant as standard transaction but still no positive result. Its working fine when i am testing it but not working when i am executing it independently.
Would appreciate your replies. Thanks

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.

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

Create transaction variant of mm01 - can't fix material type

Hi,
I am trying to create two transaction variants for MM01 called ZM0R and ZM0F for raw and finished materials respectively.
I have created them and all the fields I want as Required are working.
However, I want the material type to default in as raw for ZMOR and as finished goods for ZMOF. I have ticked "with content" and "required" but it is not working. Whatever material type was last used in MM01 still comes in.
I have also tried creating a copy of MM01 using Se93 to see if I can get it to work this way but when I test it, I get a message Sap Transaction control and can't seem to get past that.
Any ideas?
Thanks

Hi Jurgen,
worked a treat, thanks!. I have another related problem...my backflush field in MRP2 is not appearing. I have checked the field groups and it is there, group 74, for the material type and marked as Optional. Is there somewhere else this can be hidden?

Two Transaction Variants to one sales order type

I want to assign two different transaction variants to one sales order type.
Scenerio is this that i want to show billing block filed for order type "cr" for user SD1 in display mode and same filed for order type "cr" in changeable mode for usr SD_manager
thanks in advance

Hi
Instead of going with Transaction variants go with Authorization check , so that your requirement can be fulfilled , say if document type CR is in display mode then give authorization to release the billing block. But if the document type CR is in change mode then give the authorization change mode . Then your requirement can be fulfilled.
Regards
Srinath

Transaction Variant for a standard report without transaction code

Hi,
I want to create a transaction variant for a executable report. The report has some subscreens 100, 110 etc. I want to hide the subscreen through transaction variant. So I have created a transaction code (Y*) for it and then tried creating transaction variant using SHD0 transaction. But the fields are not listed to choose invisible or other options. Please advice

The fields are listed when you leave each recorded screen. You have the flag "do not display the screen". It's strange you don't have anything, are you sure you started the recording? (you enter the transaction code, the transaction variant, you click the Create button and the screens are displayed and recorded)
Which transaction is it?
A little remark (about your last posts): forum rules ask people to give points, it's a way to say thank you. Otherwise, people won't help you anymore. It's not a black and white logic : don't give points only when your problem is solved. Give 2 or 5 points to thank people (or 0 if it's out of context). Thanks.

Problem in transaction variant of standard transaction

I am making transaction variant of VA01 throught t-code SHD0
and i have to make tab item overview invibile , i do that and also created t-code for the variant ,
but when i run that it is still visible can anybobdy tell y ??
suitable answers will be awarded points
Edited by: Akash Jain on Apr 2, 2008 8:56 AM

Hello Simon,
here you are my answers:
1. Yes, I've run both ipak and RSA3 in the same mode (full), with the same selection parameters.
2. I find this suggestion about debugging background processes very useful. I've been wondering several times about how to debug pieces of code in similar situations but could never find a good solution: now I know how to do in these cases. Thank you!
In this specific case, to see what was going on in the extraction process in R/3, as an alternative to debugging I have put some logging messages in the cmod code with the WRITE statement, and then inspected the spool output of the ipak execution.
The result of this test was that the query for selecting the LIFNR value
select single lifnr into mov_cdc-lifnr from mseg
       where MBLNR = mov_cdc-REFBN
       and MJAHR = mov_cdc-REFGJ
       and ZEILE = mov_cdc-REFBZ
       and MATNR = mov_cdc-MATNR
       and WERKS = mov_cdc-werks.
fails (sy-subrc = 4) because the fields REFBN, REFGJ and REFBZ are not filled (initial) in the extract structure passed to the custom function module.
When the extraction is executed with RSA3, instead, the above mentioned fields are filled and the query works correctly.
Thank you so much for your suggestions.
Regards,
Virginio D'Amico

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.

"transaction variant" functionality in the Web Client

I'm opening this message for a customer this message is a consulting...
Thanks in advance,
Daniel Kaoro Kobashigawa
In the SAP GUI we have Transactions that use transaction variants. For example we have ZBUP1A that is based upon BUP1. It uses a transaction variant to default certain important fields like "Grouping" "BP Type" etc. so BP are created correctly.
We are in the process of CRM 2007 upgrade from CRM 5.0 and plan to use CRM WebClient UI for all user transactions.
1. Can we put to use the same Transaction variants for the CRM WebClient UI without using the Transaction Launcher to call the GUI transactions (as SAP does-not recommend the use of SAP GUI Transactions except for
administrative related functions)? If so is it just configuration?
2. If we cannot use the Transaction variants for the CRM WebClient UI, is there a way to pass parameters to the standard transactions by making modifications to the logical links provided in the Navigation Bar? If so, please elaborate.

Discarded question

Problem in creating transaction variant

Hi all,
I am trying to create transaction variant for F- 41 transaction . it's giving an error message .
Variants are possible only for dialog transactions.
Message no. MS417
Diagnosis
You cannot create variants for variant or parameter transactions.
Procedure
Variant transaction: Adjust the variant
Parameter transaction: Adjust the parameter(s)
i need to disable the filed 'document type' .
Guide me.
Regards,
Ravi

Hi,
You can copied into SAP standard program to Zprogram and then use the Loop at screen....Endloop to disable the Documnet type.
FYI...If you go for F.14 transaction there you find Sytesm----> status .. there you will find SAP standard program. Make a copy to Zprogarm and try to disable it.
Regards
Thiru

What is a Transaction Variant?

hello abap gurus,
can u tell me what is a transaction variant and how does it works? i have a requirement that is to run an existing customized report program in the background. that means no user interface. i'm pretty new with abap programming. please help...
thanks,
sid

Use SE75 to create your own custom text ID for SAVE_TEXT object
Finding a user exit when you only have the function module name: Use table MODSAP with member=function module. This will give you the enhancement name that you can enter in SMOD.
To execute on OS command in SAP: Use program RSBDCOS0
Transaction Variants
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
tables: tbtco.
data: jobcnt(1) type n,
      t_sdluname like tbtco-sdluname,
      t_strtdate like tbtco-strtdate,
      t_strttime like tbtco-strttime.
ZXXX is the job name to check for
select * from tbtco where jobname = 'ZXXX'
                      and strtdate = sy-datum
                      and status   = 'R'.
   add 1 to jobcnt = jobcnt.
    if jobcnt = 1.
       t_sdluname = tbtco-sdluname.
       t_strtdate = tbtco-strtdate.
       t_strttime = tbtco-strttime.
    else.
       exit.
    endif.
endselect.
if sy-subrc = 0.
   if jobcnt >= 1.
       message i999(b1) with t_sdluname ' has released job on '
                         t_strtdate t_strttime.
   endif.
endif.
Use Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
Using Transaction variants
Change SAP standard screens by hiding fields, screens, tabstrips, changing field properties, ... read on
Show all users per Application server
Transaction AL08
To log a user off via an ABAP
CALL 'SYST_LOGOFF'.
Advanced SM04 program
The following program displays the Ip address , workstation name , Nt user name etc. Plus you can send instant messages to users just by clicking on the user name. It will show a red band for users who exceeds session limit. ( That you can adjust ). Created this for R/3 4.6C and above. (Submitted by Joy Ramachandran) - Click here to download zuser.txt
Changing the SAP Logo on the top right of the SAPGui
Change file sapalogo.bmp in directory C:\Program Files\SAP\FrontEnd\SAPgui\themes\default (SAP 4.6C)
Changing the Logo on the Right Hand Side ( Courtesy of: http://sapr3.tripod.com/ )
Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif       EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description : Company Logo
Click Import and specify the filename where your GIF file is located.File type is BIN. Finish press the Transfer button.
If successful, your logo will be shown in the Binary data for WebRFC.
Transaction codeSM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name                     Value to be set
START_IMAGE      ZXXXX.GIF
RESIZE_IMAGE     NO
Logoff and Login again
Automated transports
regards
vinod

VA01 - transaction variant - NO_VARIANT

Hello all,
We created a transaction variant for VA01 to make one of fields in VA01 display only for certain users. To make our transaction variant work, we used NO_VARIANT variant in VOV8 transaction. Our transaction variant is working now but in VA01 trasaction we are getting additional fields which we did not see in VA01 before using NO_VARIANT in VOV8. We are certain that NO_VARIANT is bringing in more fields into VA01. Can we modify NO_VARIANT or is there a way to avoid additional fields that are coming in becuase of NO_VARIANT? Please let me know.
Thanks,

Hi,
It's not recommended to change standard variant. But you can copy variant NO_VARIANT to ZNO_VARIANT by transaction SHD0 and copy transaction variant to your own name and copy too variant screen NO_VARIANT_0101 to your own ZNO_VARIANT_0101. After you can change value and assignment. And assig your Z....variant to the dicument type with VOV8.
Rgds

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.

How to assign screen variant to transaction variant

Hi ALL
I HAVE CREATED A SCREEN VARIANT HOW TO I ASSIGN IT TO TRANSACTION VARIANT , PLS GUIDE ME ON THIS ITS IMPORTANT

Sunaina,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful
Regds
MM

Standard SO type overwrites transaction variant

Similar Messages

Maybe you are looking for