Create cross-client selection variant

Hi,
Can anyone please let me know how to create a cross-client selection variant. I am trying to run a report with a default selection variant but will require the variant to be available in all clients. I'm working on an R/3 release 4.6b system.
Regards,
Andy.

Hi,
Create variant prefixing "CUS&" followed by variant name, this will create a system variant and ask for a TR. the variant thus created will be available in all clients, If not you can just import the Tr created to all client using transaction SCC1.
Award points if found usefull
Regards
Simin.R

Similar Messages

How to create cross-client variant?

Hi Experters:
Can someone tell me how create cross-client variant in ECC6.0?
in 4.6, we can define the client or define cross-client transaction variant,
how to create cross-client variant in ECC6.0?
Regareds,

Hi,
In se93 there is a check box cross-client .
The Cross-client switch identifies which transaction variants are cross-client and which are client-specific. If the switch is set, the transaction variant is cross-client. If the switch is not set, the transaction variant is client-specific.
A client-specific transaction variant can only exist in the client where it was created. The field contents of the transaction variant only have to be available in the particular client. A cross-client transaction variant is available in the system regardless of which client is currently active. The field contents of the transaction variant have to be available in all clients.
http://****************/Tutorials/ABAP/TransactionVariant/Create.htm

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

Selection variant for a report painter

Hi,
I created a report painter report. I want to create a default selection variant for a specific user. For example, I want user GIRARDJU to have company code=ADM, period 6 to period 13. I tried to create a variant and call it U_GIRARDJU but it doesn't work like it does for the standard SAP reports...
Any suggestions?
Thanks a lot,
Julien

Hi,
First go to the report you have created.
Then save the selection criteria you want & give an appropriate name to your variant (eg: /INOKA).
When you execute the report next time, this variant will be there, & by double clicking it you'll get the saved information.
Best regards,
Inoka.

How to create a cross-client table maintenance dialog?

Hello everybody,
I have a client specific table (mandt is the first key field) that should be maintained cross-client: In the table maintenance dialog, I want to change/create/insert values belonging to clients other than the current logon client. Can I do this with a generated maintenace dialog? If yes, how?
Thank you for your help, regards, Kathrin!

Hi Kathrin,
I think you can't, you must create your own dialog maintenance program.
They are some program to copy data from client to others .. but never seen any dialog cross client. (or remove the mandt in your key).
Regards
Frédéric

Creating a User-defined Selection variant for Transaction ME21N

Hi,
In transaction ME21N with the 'Document Overview' feature turned on we can view a list of standard selection variants. I would like to add a user-defined selection variant to that list. There is an OSS Note 377180 present which describes how to do that but(as per transaction SNOTE) that note cannot be implemented in our system. Is there any other way to get that done?
Any help would certainly be appreciated.
Thanks,
Alam.

So I am having a similar issue. I have a fixed length flat file with 3 different record types.
1 a header ( length is 82 bytes with the first byte set to H ( single record always the first )
2 a detail record ( length is 382 bytes ) with the first byte set to D ( multiple records )
3 a trailer record ( length is 82 bytes ) with the first byte set to T ( single record always the last )
I created a UD OTD with 3 elements for each record type, RECORD_TYPE is the first field 1 byte. Matching for each on either H,D, or T. When I try and test the OTD with the Run Test button I get an unmarshal error
<SOD>""<POS>"HACCUMULAT..." failed input match, Fog#431, after <no path>: failed node: trailing junk in fixed/parent
HACCUMULATED BENEFIT TRANSACTION FILE 20080801 20080825 0 0
D ar3531 ar3531 ar3531 ar3531000 55887027260 30.000 30 5098765 20080804 000T114 120080806 82820P30000001024511 25.00 0.00 25.00 0.00 25.00 25.00 0.00 0.00 0.00 0.00 0.00T
TACCUMULATED BENEFIT TRANSACTION FILE 20080801 20080825 2894 0 0
Not sure whats going on, so if anyone has any suggestions on where to look that would be great
Thanks

How to Create selection variant in ABAP

Hi all,
i want to create variant selection in get data of the variant on my ALV Grid.
See on the screenshot my problem :
http://www.casimages.com/img.php?i=101006040413882278.jpg
Thank you very much for your answers.

i Want to make new functionnality of my program which permit user to Save a selection variant with the result of the alv (Mark row)
It is a new variant and this variant is use for the same program.
In fact this functionnality permit to the user to make a variant selection with a selection of article without knowing the reference of article.
Thank you very much.

Create source system without cross client config

The SAP-Help URL given below explains the prerequisites for linking BW to a source system. One of the requirements is that the source client is open for cross client configuration.
Is there a way to create the source system without having cross client rights in each source client?
I understand that the client only has to be open while it is being linked to the BW system but I would prefer to avoid opening the client at all.
Help URL:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm

Hi ,
You can perform the following check :-
1) Check if BI DBMS and Source DBMS are same. If not then you have to Install DB Client for that Source then this error should not come.
2)Check if DBSL(Data Base shared Library is installed in BI for this Source. If not Kindly Install that in BI server.
Kindly perform these operations and lets see what happens.
Regards,
Amit Kumar trivedi

How to create column selection variant for VA05?

Hi Experts,
How do I create column selection variant for VA05?
Thanks,
Sachin

Hi,
Goto SU3, enter user name and press enter
goto parameters tab, enter parameter ID SD_VARIANT_MAINTAIN and parameter value 'A' and save.
Now check in VA05, you will get save button in active mode.
Regards,
Chandra

Create a user-defined selection variant in transaction ME21N

Hi,
In transaction ME21N with the 'Document Overview' feature turned on we can view a list of standard selection variants. I would like to add a user-defined selection variant to that list. There is an OSS Note 377180 present which describes how to do that but(as per transaction SNOTE) that note cannot be implemented in our system. Is there any other way to get that done?
Any help would certainly be appreciated.
Thanks,
Alam.

I would suggest that you replay the transaction with breaks, so that you can see exactly what is happening (in the start options, set the SAPGUI replay options to stop at each ProcessedScreen)
It may be that the Selection Variant button is not present during replay. In this case, you would need to make the step where this button is pressed as optional.
ME21N is a difficult transaction to automate because it always remembers what you were last doing in it and restarts the transaction from that point. You can delete the user settings (so you always start the transaction as though for the first time) using the following code in your script:
ABAP.
* Delete all User-Settings in MM
DELETE FROM ESDUS WHERE UNAME = SY-UNAME.
* Delete all User-Settings in search help
DELETE FROM DDSHDEFSH WHERE USERNAME = SY-UNAME.
ENDABAP.

Issues with creating transport request for cross client changes???

Hi,
In our ECC 6.0 dev system, functional team makes all their configurations in client 100.But ABAP team is using another client 120 to create /modify ABAP objects.
So all workbench requests getting created in client 120.
I would like to have all customizing/work bench requests created and released from client 100.Is is possible to re-assign all work bench requests created in cleint 120 to client 100?
Thanks
Ram
Message was edited by:
        rama subramaniam

Hi Rama,
             If u r making any workbench changes that means they are repository
             objects it will reflect entire system. I dont think we need to import them
              into the same system once again. Hw ever we can do that by scc1.
Regards,
Vamshi.

Dynamic creation of date in selection variant

Hi All,
I have a Z program for updating a field in BOM item. One of the input field in the report is "Valid From Date". Actually the current date is automatically fetched through a function module and it is defaulted in that field.
Our client is using selection variant for ease of use. The problem here is old date in the selection variant is replacing the current date. I want current date to be created automatically during insertion of variant also. How can i solve this problem. Is there any selection variable inside the variant for dynamic creation of Date?
Thanks
Sankar

As I know there is no setting for this. For any std or Z report variant function with L should act same way...anyway you discuss with your ADABer.
See the help for variables
Selection Variables
The following three types of selection variables are currently
    supported:
o   Table variables from TVARV
        You should use these variables if you want to store static
        information. TVARV variables are proposed by default.
o   Dynamic date calculations:
        To use these variables, the corresponding selection field must have
        type 'D' (date). If the system has to convert from type T to type D
        when you select the selection variables, the VARIABLE NAME field is
        no longer ready for input. Instead, you can only set values using
        the input help.
        The system currently supports the following dynamic date
        calculations:
        Today's date
       From beginning of the month to today
       Today's date +/- x days
       First quarter ????
       Second quarter ????
       Third quarter ????
       Fourth quarter ????
       Today's date - xxx, today's date + yyy
       Previous month
o   User-specific variables
       Prerequisite: The selection field must have been defined in the
       program using the MEMORY ID pid addition. User-specific values,
       which can be created either from the selection screen or from the
       user maintenance transaction, are placed in the corresponding
       selection fields when the user runs the program.
The SELECTION OPTIONS button is only supported for date variables that
   fill select-options fields with single values.
i.e means we can do that with D also.

How to disable Cross client Table Access

Hi All,
i have created a Sand box client and i have set its cross client object value to
"No Changes to repository and cross client customizing objs"
but still users are able to run transactions like SR13 which are cross client tables
please help

HI Zeeshan,
Once u run the Tcode like SR13, the users would be able to enter the Tcode and have a new entry varinat created..but during SAVE the system would sure prompt the message... " Changes to Repository or cross-client Customizing are not allowed. Please press DISPLAY or CANCEL" ..
so the changes would not be saved hence forth and have to be cancelled out..
hope this is what u have been looking for..
Br,
Sri
Award points for helpful answers

How to create transaction or screen variant for custom tcode in module pool

Hi,
I have one module pool program with custome tcode ,i want to create transaction or screen variant for this tcode.Next time when we run this tcode we need a variant for this tcode.
I tried by using of SHD0 but it is working only for standred tcodes.Is there any possibilty please help me.
thanks,
Lavanya.

Hi,
you created a Custom Tcode for ur module pool Pgm..if u execute the Tcode in the output screen give the input details and press Save Option then variant will be created. Then you can use that variant.
otherwise.. while creating a Tcode..
select an option for Tcode type Tranasction With variant ..there u will provide the variant for ur Tcode ( which is already created ).
Regards,
PraVeen.

How do you make report selection variant the default selection varaint?

Hello all,
I know how to create a Selection Variant for reoprts and I know how to create a User Variable that defaullts field values for a specific user. But can anyone tell me how do you have a specific Report Selection Variant Default for everyone? I know this one is probably staring right at me but I'm not seeing it. Your help would be greatly apreciated.
Thanks,
Dan

Bhatia,
That will only hold the data for that specific user. You can also do that via "user variables". What I would like to know is how do you get it to be the default for All users.
I am investigating the possibility of using t-code SE38 and changing the Values on the existing variants to contain the default data we'd like to see. I'd much rather create just one Variant per report and have that be the default variant.
Anyone have any ideas?
Thanks,
Dan
Edited by: Daniel Goodhart1 on Oct 7, 2009 11:03 PM

Create cross-client selection variant

Similar Messages

Maybe you are looking for