Reg variants

hi all,
i have a doubt regading variants.please tell me what is the difference between variants,screen variants and transaction variants.and i want to know how they are utilised in sap.please let me know step by step process to customise them
regards
ravi

hi ravi,
Welcome to SDN forum.
Check these threads on discussion about variants.
variants
Re: variants
Deleting Variants
Re: how to delete variants
Transaction variants
Transaction variants (SHD0)
program variants
Re: program variants
screen variant
screen variant
Reward with points for Helpful answers
Cheers
Alfred

Similar Messages

Reg:Variant Dependencies & Pricing

Hi Gurus,
I have configured up to the below mentioned steps.
1.Creation of Material Master Record with required settings
2.Creation of Characteristic and it's values
3.Craetion of class
4.Assign characteristics to Class
5.Create configuration profile and assign it to MMR
I have strucked at pricing and dependencies maintenance.I need some info.related to pricing maintenance and dependencies creation.Kindly help me on this regard.
Thnaks & Regards,
Sash.

Hi,
The following needs to be set up for the variant pricing of configurable product .
Create pricing condition VA00 for the variants
Create characteristics
Create variant table
Create dependencies
Allocate the dependencies to the configuration profile
Procedure:
1)Create Pricing Condition-VK11 Transaction code.
Condition Type:VA00
Maintain the required pricing here.
Note:The condition type VA00 is defined as a fixed rate surcharge, which is applied to the base price of the product ordered. This variant condition is created as part of the pricing master data for each of the configurable options for which a surcharge should apply
The condition type VA01 could alternatively be used in variant pricing to increase the price of the higher level material by a fixed percentage rate.
Maintain the prices for all the variants (Characteristics) you have create.
Note:The entry of the Variants is case sensitive.
2)Create Characteristics:Surcharge
Transaction code:CT04
Create a Characteristics name to identify your Pricing Characteristic.
In the addition data tab maintain the following:
Table Name:VKOND and Field name :SDCOM.
Note:
The characteristic u201CSURCHARGEu201D references to the field u201CVKONDu201D of the u201CSDCOMu201D table. It provides the link between the materialu2019s variant configuration and the variant conditions that were entered.
3)Create Variant Table::
Transaction code:CU61
Maintain the characteristics in the Variant table.(Char.Name,Char.Value,Var.Cond )
Save it..
4) Maintain the Variant table :
Transaction code:Cu60
Maintain values for Example
Characteristic Name   Characteristic Value Variant condition
Size                                     10                             Size_10
Colour                                  Red                         Colour_Red
Colour                                  Blue                          Colour_blue
Save the table.
5)Create Dependencies:
Transaction code:CU01
Maintain the required description and in dependency editor
You see the screen u201CEdit Dependencyu201D. Select Insert line icon five times to insert lines. Enter the following on the inserted lines.
TABLE TBL_PRICING
     (CHAR_NAME = 'Size',
      CHAR_VALUE = $self.Size,
      VAR_COND   = $self.SURCHARGE).
Note: This procedure references the Table TBL__PRICING. The dependency checks to see which value was chosen for the 'Size' Option and specifies the appropriate Variant Condition to this choice.
Check whether your dependency has errors or not.
After that Save it and make sure that it has been released(Which you can find in the initial screen)
6)_Allocate Dependency to the Characteristics profile of the material:
Transaction code:CU42
In the screen u201CChange Configuration profile for Material: Profile Overview u201D. On this screen, maintain your profile and select Profile Detail icon.
You see u201CChange Configuration profile for Material: Detail Screenu201D. Under the Section Header Basic Data, select Object dependencies button.
You see the screen u201CMaintain Dependency: Allocation to Objectsu201D screen.
Maintain your dependency here in this configuration profile for the material.
Once it is done cross check in transaction code 'PMEVC' Transaction code for ECC 6.0.
Simulate your Variant configured material and cross check.
Hope it helps.
The steps may look little bit exhaustive but the process of maintaining it shall be fruitful.
Have a Nice Day.
REgards,
Ravi

Reg:Variant configuration

Hi,
I have created a sales order, ran mrp converted planned order to production order
1) at the time of creating Production order if i press Material lists button it says no material exists ,but already i have cretaed pr/Purchase order,done gr for the raw material
2) At the time of confirming the production order in co11n after entering the confimation qty, if i press goods movement
iam not able to see the raw material
Kindly help me in solving this issu
Also tell me the configuration settings i need to maitain in Shopfloor control
Regards,
Raj

Raj,
Not much info to go on.
Do you have a valid BOM for the Finished goods part that points to the Raw Materials Part? CS03 > enter FGs material; plant in your sales order; Bom usage 1; validity date earlier than the start date of your production order. Does it exist? Are the expected RM components there?
If yes, look at your config for production order.OPL8. Under BOM Application, what is there? is the Bom Application relevant for explosion? You can see the relevancy in OPJM
General PP settings (including SFC)
http://help.sap.com/bp_bl604/BBLibrary/Documentation/142_BB_ConfigGuide_EN_IN.doc
General Variant settings
http://help.sap.com/bp_bl604/BBLibrary/Documentation/147_BB_ConfigGuide_EN_IN.doc
Best Regards,
DB49

Reg : Variant saving for Module Pool Programming

Hey Friends,
Plz help me in how to create variant for Module Pool Programming as in normal reports.Thanx in advance.

Hi,
You can create variants for Module pool program using the transaction SHD0. You can create Screen variants for your screens using this Tcode.
Go to SHD0 -> Give the Transaction code(ZTRAN) for which you want to create a variant -> name of some variant (ZVAR) -> create -> takes you to your transaction -> Give the values that you want to be displayed as variants -> Click on Save -> Opens a pop up to confirm the screen entries -> Check the check boxes of those fields that you have entered the data with (the column with check boxes that says W.Content) -> Exit and Save -> Save the variant -> You can see a screen variant created (ZVAR_0100)
Now Goto -> Create variant transaction -> Give your transaction variant name (ZVAR) -> Select Transaction with variant -> Takes you to SE93 transaction -> Give the transaction variant name -> save. Run with the created transaction.
Edited by: Nitwick on Jul 27, 2009 4:49 PM

Reg: Variants Deletion

Hi Every one,
Iam using one function module to delete the variatns 'RS_VARIANT_DELETE', with this function module
i can delete only specified variant only, But i want to delete all the variants at a time with out specifying.
any function module is there ?.
Best Regards,
Narasimha Rao.

Hello Rao ,
I didn't find ny FM , but I hope it may help you
mostly all the variants are stored in table "varid" & "varit" ,
try to write a report , so as to delete all the variants belonged to Z* or Y* programs.
Delete from "varid" & "varit" directly.
Regards
Aby.
Edited by: abhi on Nov 11, 2008 7:04 AM

HI Gurus Reg - Variant Configuration

HI gurus
Can any body explain the
$parent, $root, $ self
and how to use that
documents i have checked and of not that much help ful
thanks in advance
Rajesh

Hi Rajesh,
These all are Object Variables:
Object Variables
You use object variables in a multi-level configuration, to describe configurable materials in a configuration structure.
You can use the following object variables:
u2022 $ROOT is the highest-level configurable material in a configuration
u2022 $SELF is the material to which the dependency is allocated
The material to which an action or procedure is allocated is the same material for which values are inferred by the action or procedure. To make it clear that actions and procedures only infer values for materials to which they are allocated, the characteristics are preceded by the variable $SELF.
In dependencies that are allocated directly to the header material, $SELF and $ROOT both mean the header material.
u2022 $PARENT refers to the object immediately above $SELF in a multi-level configuration.
The variable $PARENT has no meaning for the header material, because the header material has no superior materials.
In dependencies that are allocated to BOM items, $PARENT refers to the configurable material for which the BOM was created, whereas $SELF refers to the material of the BOM item.
However, in a multi-level, interactive configuration $ROOT may refer to two different objects:
u2022 If the BOM is exploded in production, $ROOT always refers to the material that transfers requirements.
u2022 If the BOM is relevant to sales and distribution, $ROOT always refers to the header material.
Hope it helps!
Preethi

Disable standard Button in V_V2 tcode

Hi,
In Standard tcode V_V2 , there is one button called CHANGE DOCUMENT i want it should be desiable .
How to change button view to disable mode in stanadard tcode.
i M using SHD0 , but not familiar with its setting.
can any one explain it . In detail , Step by Step.
Thanks.
Jim

Hi,
Please check for my answers here
[Hide button and Menu in transaction variant;
[Re: Reg : Variant saving for Module Pool Programming]

Different shop variants / reg. customer doesn't work

Dear Experts,
we customized two different shop variants.
1) for switzerland with swiss francs and 7.6% VAT
2) for germany with euro and 19% VAT
Now we have following issue:
If we use an existing registered customer (original add in shop variant 1) for shop variant 2 we don't get in the basket prices.
In the basket and after the payment side all products are with the value 0.-.
If we use an new registered customer for shop variant 2 all prices are okay.
Now our questions:
It's possible that customers can shop in different variants? If yes what we need to do?
Thank you very much in advance for your help.
Kindest regards
Jannis

Dear Srinivas,
we use the B2C scenario.
Thanks
Jannis

Reg. copying Layout Variants from 1 ALV pgm to another

Hi Friends,
I am currently copying an ALV program Ztest1 to ztest2 through ztest5. While doing so I want the LAYOUT variants that are available for ztest1 also to be copied to these other programs.
All I am aware is that the table LTDX stores all the layout variants for a particular program.
Could anybody provide me the right inputs on this.
Thanks in Advance.
Rgrds,
Gayathri N.

I took this approach and it worked for me:
1) Change your program so that everytime an ALV function is called it is using the original program name in the variant declaration, ensure you keep the original code commented out, you will need to put it back later. Examples:
FORM variant_init USING varname TYPE slis_vari.
    CLEAR g_variant.
   g_variant-report = g_repid.
    g_variant-report = 'ORIGINAL_PROGRAM_NAME'.
FORM f4_for_variant.
   g_variant-report = sy-repid.
    g_variant-report = ORIGINAL_PROGRAM_NAME.
    CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
FORM check_variant.
    IF NOT p_vari IS INITIAL.
     g_variant-report = sy-repid.
      g_variant-report = ORIGINAL_PROGRAM_NAME.
      g_variant-variant = p_vari.
      CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
2) Display function lt_variant_save via SE37, set a breakpoint at the first executable line:
     perform variant_save tables it_fieldcat
4) Run your program with the layout variant you wish to copy.
5) Hit Save Variant. You are now in debug mode.
6) Enter variable CS_VARIANT-REPORT in the variables 1 panel.
7) Double-click on CS_VARIANT-REPORT.
8) Hit the Change Field Content button
9) Change the value to the name of your new program, then hit Enter.
10) Hit Execute (F8). You have now saved the variant under your new program name.
11) Exit and rerun your program as necessary for as many variants as you want to copy
12) Change your program back to using sy-repid (or whatever else it was referencing) wherever you changed it in step 1.
13) The variants have now been copied and you can run your program with the new variants.

REG:ALV Variants

Hi all,
I am working on an ALV List display.in the output If you select the magnifying glass and display item detail, or change the display variant, the header information on the report (User Name and Report Name) repeat themselves.
How can i get the user name and report only once when ever i execute the report.Plz reply as soon as possible if any.

Hi,
You can use CALL METHOD cl_gui_cfw=>dispatch.
Hope this helps
Regards
Sunil.M

REG copy of transaction variant for VA01

Hi,
I need to copy transaction variant for VA01
After copying transaction variant
i tried to copy screen varaiants for 4440 its working fine but for screen 4480 the fields which are to be invisible is not working
i tried to use same screen variants still not working
please suggest if any customization needs to be done.
thanks ,
kamalakar

Hi,
I guess you don't have assign the transaction variant in TVAK.
Instead you could have created the z tcode by using the option "transaction with variant(variant transaction)" and given the transaction variant.
Thanks
Naren

Reg internal table and variants

Hi,
Can any tel me
1. how to create internal table dynamically ( i knew its done thru field symbols but i dont know how) ...pls i need a clear example..pls
2.I have got a requirement where i need to display the fields in ouutput based on the variant i choose/select at selection screen.. that means the fields should be varying based on the variant chosen at selection screen..
pls i need a good example for the above 2 queries..plsss
Thanks in ADVANCE
Jay

hi
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb387a358411d1829f0000e829fbfe/content.htm
Regards
Anuj

Reg:Process variant still red while request in green

Dear All,
Repeat Delta process was success in InfoCube and request is in green status while in process chain process variant still red until repeat process variant 2 to 3 times then only process variant turn into green at same time my process chain subsequence process not triggered please guide me
Regards,
KP

Hi,
For the subsequnt process to finish U can run a FM: RSPC_PROCESS_FINISH
RSPC_PROCESS_FINISH is a Function Module...........U hav to copy the detals from the table RSPCPROCESSLOG.........
Check this blog:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Once the Chain got Completed...to fix the issue permanently...Once try to deschedule the chain..then again Schedule it back..hope this issue will not come again..
rgds,

Reg: Test Configuration with Default variant

Hi Guru's
I am new here.. Guide me to achieve this.
I do created the Test script ,Test data and also the Test Configuration
Whats my problem is I do run the TC with external variant (File that i have mapped) .
its works fine but Default variant is not triggering all other variant are triggering.
What to do to run all the external variant including default variant . Guide me with steps.
Thanks in advance
Regards
Anandh

Hi Anandh,
ECATTDEFAULT is a special variant which is not intended to be uploaded from external files.
If you use the download option to prepare your external variant file as a sample, you will see that ECATTDEFAULT is deactivated by using * in front. It's only downloaded to the sample file for giving the scripts import parameter defaults as a reference.
If you like use these default values for individual fields of other variants simply leave those fields blank in the other variants.
To have your test executed with the whole record of ECATTDEFAULT simply copy the *ECATTDEFAULT line in your external data file and give it an other similar name, e.g. ECATTDEFAULT1.
Kind regards
Jens

Reg. VAriant

Hi all,
Iam calling a subscreen from my selection screen.
From the subscreen I am generating another screen using free_init_selection and free_init_dialog.But the data Iam entering in these screens is not getting saves as a variant. Could anyone help me in this regard.
Thanks,
keerthi.

Hi Peter,
From help.sap,
A variant is user-defined grouping characteristic of the Scheduler. Every InfoPackage and every InfoPackage group is assigned to a variant. There are no empty variants, which means you must create a variant. The variant can be up to 12 characters in length and is case-sensitive. The system only recognises the variant when you have created and saved an InfoPackage (or an InfoPackage group) for the variant.
After saving a change in the Scheduler, the variant is also saved so that the variant is there for the user when he/she next calls up the Scheduler.
You cannot delete a variant.
Regards,
R.Ravi

Reg variants

Similar Messages

Maybe you are looking for