Variant Attribute

Hi,
Could you please explain me what is variant attributes ?
Thanks & Regards,
Shailesh
My GMail ID is
shaileshbhise1978
@ gmail com

Hi Shailesh,
you can find informations here:
http://help.sap.com/saphelp_scm50/helpdata/en/c0/980374e58611d194cc00a0c94260a5/frameset.htm
under "Attributes of Variants".
I hope this helps.
Regards,
Tibor

Similar Messages

  • FAGLL03 or in FBL3N Display of Line items by variant attributes

    Hi Guru's
    In FAGLL03 and in FBL3N, when I select fiscal year and posting period fields from dynamic selection and in Variant attributes under dynamic selection for fields Fiscal Year and Posting Period ,selection type S ..for type Selection variable I selected T i.e T: Table Variable from TVARVC and in Name of Variable (Input Only Using F4) I selected Variable name.
    I want the line items to be displayed for fiscal Year and Period that is maintained in that Table. i.e as per our client our fiscal year is 2012 and Period is 2 , this values are there in tht table but when I select the variant in Both FBL3N or in FAGLL03 , its displaying complete details.
    as a work around I have given fiswcal year and posting period manually..which is not my requirment.
    I want to add this variant to a batch job so tht it will automatically pick the report with current details.
    Please Suggect and help ..
    Thanks in advance
    Goutam

    Issue is Solved.

  • How to hide input fields on selection screen using variant attribute

    Hello all,
    I want to know how to hide input fields on selection screen using variant attribute conpletely.
    As you know, when setting the attribute of variant "Hide field" checked, the field is temporarily hidden, but when clicking "All Selections(F7)" button on the selection screen, the fileds become appeared.
    I want to hide the field completely. Di you know how to do ?
    Thank you for your support.
    Regards,
    Hideki Kozai

    Use this attribute hide field and save the variant. Then create transaction for this program setting default variant for parameter Start with variant . The user who runs it will have it by defualt set.
    Otherwise
    in PBO simply use LOOP at screen and output = 0 for this field. This will ensure that field is invisible in any case.
    Regards
    Marcin

  • How to add Variable in variant attributes in query

    Dear all,
    User required to add one variable (e.g. Last Week date) in variant attribute.
    For example: If we select D: Dynamic date calculation then in that case i want to add one variant attribut (Last Week).
    How i can maintained this.
    Thanks in advance.
    PM

    Dear All,
    I want to Add Variable name to Dynamic Date Calculation List as Last Week.
    How i can create variable for Last week.
    Thanks in advance.
    PM

  • Get variant attribute

    I m using LV 6.0.2, the function "get variant attribute" does not work. I
    get nothing out of it: no error, no values.
    Any idea?!
    Actually I could need exactly the string that is shown in a variant
    indicator/control.
    e.g.:
    'Cluster': cluster of 2 elements
    'Array': 1-D array of
    'Numeric': double
    'Boolean': boolean
    'Array' -> (2.000E+0, 2.000E+0)
    'Boolean' -> FALSE
    Has anybody an idea how I can get this as a string?
    Thank You.
    Max
    -> [email protected] / [email protected] <-
    -> Max Weiß * Eulenweg 2 * 76356 Weingarten * Germany <-
    -> Fax/Voicebox: 0180 505254775181 * Tel: +49 162 9114507 <-
    -> ICQ: 123429315 * DB 8 MWE <-

    The reason you can't get an attrivute of the vairant is because your variant doesn't have any. Use "Set Variant Attribute" to add an attribute to your variant, and then you should be able to read it back later using the "Get Variant Attribute".
    cheers,
    Christopher
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

  • Varying Attributes in Essbase 11.1.1.x

    Hey everyone,
    Has anyone here used varying attributes with much success in Essbase System 11? I love the concept but in practice it's been quite maddening. For example, say I want to tag Product A with a Sales Manager and Period & Year are my dimensions it will change across. If I tag Product A with Sales Manager 1 for Jan/2009 - Oct 2009, everything is fine. Then I come along and I vary the attribute for Product A, switching to Sales Manager 2 for Nov 2009 - March 2010, everything remains fine. Then I switch it again to Sales Manager 3 for April 2010 - Nov 2010. With this third action it totally scrambles up the dates, usually moving Sales Manager 1 to something crazy like Jan 2011 (I've never even mentioned 2011 in any attribute definition) - some random month in 2009! What's going on?
    And then there's the other anomoly i've come across. Say I tag Product B with Sales Manager 1 starting in June 2009. When I go to pick my end date it grays out any month choices before June (i.e. Jan-May), as if, for example, it's inconceivable to Essbase that I might want that Sales Manager assigned through April 2010. This makes no sense to me! So I tried it where I'd break the time assocation into June 2009 - December 2009, and then add Jan - April 2010 with the same Sales Manager. This works (I think) but then when I go to add the second Sales Manager starting in May 2010 my dates get all scrambled again.
    Does anyone know how to make this work in practice? The theory is awesome and would be highly useful, but it's downright maddening trying to get it to actually work.
    Finally, I am not having any luck in trying to build out these associations via dim build load rule. Is it possible to build varying attributes over time in a load rule? I don't see how it is but have a hard time (well, not that hard) believing that Hyperion would develop this and not have a way to automate the build. Any advice?
    Many thanks in advance!!

    Hi,
    varying attributes can only be edited directly in the outline with AAS. If you want to perform a mass upload of varying attributes, you should use Essbase Studio as it is the only tool with which you can perform dimension builds with VA.
    Ilker

  • Import varying attribute dimension (with a load rule)

    How do I maintain varying attribute dimensions in a model with a large base dimension? It does not make sense to manually maintain all those members in the outline.
    Is it possible to import varying attribute dimensions (with a load rule)?

    That is true for regular attribute dimensions. Nowhere, I have found instructions how to do this for varying attribute dimensions (aka slowly changing dimensions) that change over time.

  • Hyperion Planning and Varying attribute

    Hi
    Can some help me in having varying attribute in Hyperion Planning application.
    Does Hyperion planning support Varying attribute concept?
    Regards
    Shyamkant

    HI,
    Varying attributes is applicable only to essbase so far , this is also with the advent of the new versions.
    Sandeep Reddy Enti
    HCC
    http://hyperionconsultancy.com/

  • Set Variant attributes  in  selective deletion program

    Dear all,
    I have some problem about set variant attributes  in  selective deletion program (se38)
    I want to set field fiscal year  for current year.
    Field fiscal year have selection type = "S" and i choose  selection variable. It only have Type of variable is "T"
    so i go to table TVARVC and create new variable  I've set value as below
    Selection type     S
    Number     4
    Selection value     SY-datum
    And it didn't work .
    Fiscal year still dispaly  "0".
    any suggestion?
    Many thanks,
    Big Tree

    Hi MLS,
    You can create this program using the program RSDRD_DELETE_FACTS (in SE38). You just need to provide the selections and generate the ABAP program. Ten you can use this in the process chain, with process type ABAP program.
    Hope this helps...

  • Pb with "Get Variant Attribute" LabVIEW 6

    hello
    I want to find the value corresponding to the variable name in a Variant structure. For this purpose I use the "Get Variant Attribute" function, but I do not get any good result : no result in the get value, and also when no string name input is given to get all the attribute of the variant.
    where is the bug ?
    thank you

    Hi,
    No bug, Get Variant Attribute returns values you've put in it using Set
    Variant Attribute.
    Unfortunately there is no way (I could think of) to get the text of a
    variant out of the variant in string format.
    Regards,
    Wiebe.
    "hub" wrote in message
    news:[email protected]..
    > hello
    > I want to find the value corresponding to the variable name in a
    > Variant structure. For this purpose I use the "Get Variant Attribute"
    > function, but I do not get any good result : no result in the get
    > value, and also when no string name input is given to get all the
    > attribute of the variant.
    > where is the bug ?
    > thank you

  • Get Variant Attribute Should Search for and return multiple values based on RegEx

    I am using Variants as lookup tables (see this article):
    Using Variant Attributes to Build a Dictionary or Look-up Table
    I would like to be able to use some sort of wildcard to return multiple results from the Get Variant Attribute VI (all results are of the same type, and I don't know the exact names of all the results - those two points make this idea distinct from this idea: Set/Get Variant Attribute for Multiple Attributes).
    Ideally the wildcard would be RegEx.  If it were, the means by which you specify what to return is standardized.
    In the above example, there would be some ambiguity in terms of whether or not you would want to return a result or an array of results given an input, and I doubt you could detect and assume RegEx is what the programmer desires to use.  So I think this means a new input would be required to specify whether or not the "name" input of the Get Variant Attribute VI should be interpreted as a RegEx query.
     

    Why RegEx? Why not SQL query? Why not filename wildcard matching?
    I don't see anything that makes RegEx special. For this kind of functionality, the code that you've written seems like exactly the right way to do it rather than bolting a RegEx parser or any other system into the primitives or clouding the palette with a bunch of primitives to support various search functions. I could see a primitive that takes a VI refnum that has a conpane of string in/boolean out that you would pass in to supply the filter functionality that you want for any given application, but even that I'd lean toward just letting that be a library that someone writes on top of the primitives. Yes, there is some memory reduction that can be done if it is internal to the primitives, no question about that. But there are so many variations in how to do that filtration/sorting/etc that I'm not confident that any prim would cover a sufficient use case to be worth it. I could be wrong here ... let's see what other comments come in.

  • Variable in ''Name of Variable(Input Only Using F4).' for variant attribute

    Hi All,
    I Have a small problem with saving variant.
    I am trying to save the Variant.In the varaint Attributes we have a field 'Name of Variable(Input Only Using F4).
    I  have created the PID 'XUS' in SU3.But i am not able to to view the variable in ''Name of Variable(Input Only Using F4).'.
    Anybody please let me know how to make it.
    Thanks,

    Please follow the below steps to restrict the user to access 2 company codes,
    1)Mark the IO(Company code) Authorization relavent and activate it.In the IO Business Explorer tab check the Authorization relavent check box.
    2)Go to T-code RSECADMIN -Under Maintainance -Enter the name of Authorization Object an click on create Authorization.Insert the IO and also SAP recomended Objects 1.0TCAACTVT, 2.0TCAIPROV and 3.0TCAVALID.
    Maintain the values for these objects.Select the company code and click on details.
    3)T-code RSU01-Enter the name of the user to be assigned with the authorization object and click the change button.The select the relevant authorization object and save.
    4)Create Authorisation Variable in Query Designer Create an Authorization Variable - Variable with Processing by Authorisation in Query Designer as Below for Sales Organisation
    Note : Also include all Authorisation Relevant Objects which are used in that infoprovider in addition to the above additional 3 objects otherwise you may get "No Authorisation" error when you execute the query.
    Note : 0BI_ALL is the authorization object to access all the info objects which are   authorization relevant.
    Reagrds,
    Ramitha

  • LabVIEW Variant Attributes get lost in TestStand?

    Hello,
    Example code attached.
    I'm using a LabVIEW variant as a lookup table by using the attributes (see here: https://decibel.ni.com/content/docs/DOC-25371 (and others)).  It works well.  When I attempt to pass this variant from one TestStand step to another, I lose the attributes of the variant.  I've made a small example to demonstrate this.  Am I doing something wrong?  Why does the variant retain the value, but not the attributes?  Should I store this as another type in TestStand?  In the documentation for LabVIEW types in TestStand, it is claimed that a Variant in LabVIEW maps to "Anything" in TestStand.  When I tried to use a Boolean, however, I got an error and was instructed to use a Container.  Does that container need to have some specific suptype to retain the attributes?  Or does it have nothing to do with that?
    Thanks in advance
     

    Hey GarryG,
    Here is an excerpt from the NI Product Support Engineer's response on this issue:
    "Unfortunately, this is a known limitation with LabVIEW variants in TestStand.  When LabVIEW variant data is returned to TestStand from a LabVIEW code module, the data overwrites the property. TestStand does not have a mechanism to "fit" the returned variant data to the TestStand type, so unfortunately you will need to either remap the data to the type, or use a cluster rather than a variant."
    Essentially, it appears that variant data can not be guaranteed to work properly in TestStand. In order to ensure you have your data passed from your Code Modules correctly, I would recommended following the Product Support Engineer's advice of remapping or clustering the data. If this is not possible, the Flatten Variant to String.vi could be an alternative to try. I was able to confirm that this has not been fixed with TestStand 2014 either.
    Typecasting LabVIEW Variants in TestStand Forum Post:
    http://forums.ni.com/t5/NI-TestStand/typecasting-Labview-variant-in-Teststand/td-p/2160452/page/2
    I hope this helps!

  • Make to stock planning for a finished product with variant attributes

    Hello All,
    I have one finished product with different characteristics like color and sizes, I have to create demand for the same finished product
    and to define different characteristics but should get one planned order for each combination of characteristics. Can anybody suggest how to create demand in make to stock situation.

    Hi ,
    Try using "Planning with Planning Material' .
    1: Define Planning material ( which is never produced) & it's BOM with only common assemblies( Finished product specific assmblies should not be added here)
    2: Create Finished products seperately & assign planning material to Finished products. Finished product BOM should contain common assemblies & Variant assemblies
    2:Enter Planned independent req for planning material & run MRP , it will generate procurement of it's  common componenets
    3: SO for Finished product reduces PIR of planning material & triggers Final assembly.
    4: Planning with planning material should be 60 strategy . it must be entered in both planning material & Finsihed goods.
    This is possible with make -to stock as seperate Finished goods are created for each combinatin of color & sizes.
    Hope it helps,
    Jatin

  • Incorrect terminal name for "get variant attributes" (bug?)

    According to the help, the output named "values" should change its name to "value" once we wire a name.
    This does not seem to be the case (See tip strip in image below) as tested in 2013 and 2014..
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    VariantTipStrip.png ‏2 KB
    VariantValueValues.png ‏30 KB

    In LabVIEW 2013 it changes to value if only the name input is wired. Once you wire the default value, it switches back to values. 50% is true :-)

Maybe you are looking for