Can we use Navigational attributes as Virtual Characteristics

Hi,
I need to derive the virtual characteristic based on 2 infoobjects in the multiprovider. One of the infoobject is a navigational attribute. I am using the BADI approach to create the virtual characteristic. Can we use navigational attributes to pass values to derive the virtual Char or is there any limitation.
Basically can I use the below code to read navigational attr
when <b>'0EMPLOYEE_0JOB'</b> OR '0PROFIT_CTR'.
          l_s_chanm-chanm = <chanm_used>.
          l_s_chanm-mode = rrke_c_mode-read.
          append l_s_chanm to c_t_chanm.
Thanks,
Kal

Hi Kal,
          I think you model a virtual KFig in the way you have suggested.I think the routine will work.Its looking similar populating  a field using read masterdata.I think it will work.
Regards
Karthik

Similar Messages

  • Difference between drill down and filter using navigation attributes?

    hi all,
    can anyone let me know the difference between filter and drilldown options using navigational attributes. pls explain with examples for filter and drill down and how it varies.
    thanxs
    haritha

    Jst to add up with an example :
    Say you have a cost center variance analysis report with cost elements in the filter. ( not present in the default report result )
    Filter - You can right click on a particular cost center & say " Keep Filter Value " - it will result in only showing that cost center & you can wish to select other filter value doing " Select Filter Value ".
    Drill Down - If u wish to see the cost elements associated with cost centers you can right click on Cost Center & do " Drill Down To - Cost Element " or Drill Across.

  • Issue when using Navigation attributes for filtering in BEX

    Hello,
    We are encountering an issue when applying filter on Navigation attributes in BEx query built on top of a BW HANA Virtual Provider.
    The interface is as below :
    HANA Calculation View -> SAP BW 7.4 Virtual InfoCube -> Multiprovider -> BEx Query.
    We have directly mapped the base Infoobject from HANA View to BW Virtual Provider and using this in BEx query free characteristics. We also have used the navigational attribute of this Infoobject in our Report variable screen as well as an Auth relevant object.
    Eg if ZMATERIAL is the base infoobject and ZMATERIAL__ZXYZ navigational attribute is used in the report variable screen and as Authorization variable.
    This is causing the query to fail.
    The query also fails if I apply any filter values on any Navigational attribute with error message  :
    "Termination message sent ERROR DBMAN (305): Error reading the data of InfoProvider"
    Using the navigational attribute with authorization variable fails with below :
    "Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute ZMATERIAL__ZXYZ [...]"
    Appreciate any inputs on this issue and how this can be fixed.
    Thanks,
    Tintu

    Hi Andrey,
    Thank you for your input.
    Based on the OSS note , it says to import BW7.4 SP7. We are already on BW7.4 SP7
    We get error "Termination message sent ERROR DBMAN (099): Invalid query;Failed to find attribute
    ZMATERIAL__ZXYZ"  whenever we try to apply filters on any of the navigational attribute.
    Thanks,
    Tintu

  • How to use Navigational attributes in BEx

    Hi experts,
    I have searched many threads regarding navigational attributes in BEX.
    But unable to find any info.
    How the navigational attributes are used in BEx query designer.
    What is the difference between characteristics and Nav attr in Query designer.
    Every one n saying  Nav attr are used for drill down purpose.
    What exactly is this drill down .
    Please send me any related documents also.
    Please answer me.
    Thanks in advance
    Sundar

    Hi,
    Characteristic attributes can be converted into navigation attributes. They can be selected in the query in exactly the same way as the characteristics for an InfoCube. In this case, a new edge/dimension is added to the InfoCube. During the data selection for the query, the data manager connects the InfoProvider and the master data table (u2018joinu2019) in order to fill the Query.
    Navigational attribute is like any other master data attribute except that we can navigate (filter, drill down and selection) in reports on this characteristic.
    Drilldown means after you executed the query , you want to see further detailed data with particular combination ,
    in that case you navigate further or do restiction that is drilldown.
    If you restict a navigational attribute in Query , then it behaves like a normal characteristic and not as a navigation attribute.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a63e7e07211d2acb80000e829fbfe/content.htm
    Also check the link:
    http://help.sap.com/saphelp_nw70/helpdata/en/43/f234619e3c4c5de10000000a155369/frameset.htm
    Regards,
    Amit

  • Using navigation attributes in planning queries

    Hi all!
    In one of the SAP demos I saw something like: we've got a "Store" char in planning query, and Region, Format and Climate added as free characteristics. Region, Format and Climate are navigation attributes of the Store characteristic. And when user drags, for example, Region into the planning table, he or she can enter the values on region level, and when saving the data it's being automatically distributed by all the Stores that have that Region as an attribute.
    I have a somewhat similar task - I have a "Branch" characteristic that has "Country" as a navigation attribute. I have to plan data for that navigation attribute, the country, and I expect the data to be distributed by all the branches that have that country as an attribute. But when I add it to the planning query, I've got repeating rows for each branch in each country even though I don't see the branches.
    What should I do to accomplish this task?
    Thanks!
    Best regards,
    Andrey

    Hi Gregor!
    Thanks a lot for your help!
    It's almost working as I want it to work.
    But there's something I'm probably doing wrong.
    I'm selecting B as a "free characteristic" in the query and hide it, and put B__C in the rows section, then choose "Master Data" for both "Access Type for Result Values" and "Filter value selection..." for both characteristics. After that I execute the query and see that everything seems to be as it should be, and after I enter data for something, it automatically distributes by the branches that have that country as an attribute.
    That's weird. Because when I do as you told me to, using the flag "Characteristic Rel-ps" for "Access Type for Result Values", put B__C and B in rows (B is hidden) and execute the query, I get multiple repeating rows for each branch that has the selected country as an attribute. And system tells me that "3 characteristic combinations generated successfully" (that is correct - I have 3 branches for the selected country).
    I've tried setting "Char rel-ps" for both of the characteristics, then for only one each of them - and I still get the same picture.
    Could you please tell me what I might be doing wrong here? And why it seems to be working with "Master data" chosen for "Acc. type for result values"?..
    Thanks!
    Best regards,
    Andrey
    Edited by: Andrey Makeev on Feb 3, 2012 6:45 AM

  • Can you include navigational attribute in export datasource

    Can you include a navigational attribute in an export datasource?  If so, how.
    Thanks.
    Sandy

    hi sandy,
    i don't think so. navigational attributes are not available. you need to understand that in case of an ODS object the export data source is generated out of the change log table, so if any field missing in the change log table it will not be part of the export data source.
    In case of cubes the characteristics and key figures reflects in the export data source.
    but why do you need navigational attributes in export data source ? it conflicts the nature of nav attributes as you will be storing the history statically with reference to the data when it was loaded. if you really want the same nav attributes in your subsequent data targets then include the characteristic which has the desired nav attributes in your target cube and map it from the export data source of the source info-provider. Switch on the nav attributes in the target info-providers.
    hope it helps
    thanks
    soumya

  • Using navigational attributes in selection for a forecast profile

    Hello All,
    I could understand that the forecasting can be done on navigational attributes.
    But when I goto transaction /SAPAPO/MSDP_FCST2, I could not create a selection on navigational attribute.
    Because I could not see the navigational attribute field in the selection screen for selection criteria/profile creation.
    Does anyone have any idea of how to do this?
    Also I saw the method SEL_CHANGE of BADI /SAPAPO/SDP_FCST5. But the documentation is confusing, since it says that using this method, we could delete the navigational attributes from the selection condition. Could any one suggest me how to use this BADI if I cannot create a selection with navigational attribute?
    Thanks,
    Suresh

    Hi Sunitha,
    Thanks a ton for your reply.
    The real problem is the OSS note is confusing.
    OSS Note for this method says "This method can be used to change the selection to be stored in
    in the generated selection table. Navigation attributes can be removed, such as the function of assigning a forecast
    profile to the selection can also be allowed for selections with navigation attribute without a basic characteristic."
    I am really confused what it says.
    If we can't create a navigational attribute for a selection, how could we delete it from a selection?
    Thanks,
    Suresh

  • Reports using navigational attributes

    Hi All,
    I have a question, where I need  list of queries  which use  two infoobjects(0sales_off & 0sales_dist) as navigational attributes of 0CUSTOMER.
    Is there any easier way to find out this or any table will help? Please let me know..
    Thanks,
    Chandra

    Hi Vikram,
    We fetched ELTUID from RSZRANGE table.  But RSZELTPRIO table does not have entries.
    So we mapped TELTUID field (from RSZELTXREF table) to COMPUID(from RSZCOMPDIR table) .
    This Solution is working only if selections /variables are defined on navigational attribute.
    eg: q001 -> zcustomer_0sales_dist  - simply dragged to free characteristics panel
    q002 -> zcustomer_0sales_dist  - dragged to free characteristics panel and restricted by varaible zsa_sofs
    above solution is working for qoo2 but not for q001.
    Regards
    Kusuma
    Edited by: ksheersagar kusuma on Feb 24, 2010 3:12 PM

  • Can we Retract Navigational attributes??

    Hi ,
    I am retracting PS data from BI 7 to ECC6. Can you please tell me if it is possible to retract a navigational attribute which is not as part of the cube?
    Thanks,
    Srini.

    You cant retract nav attribute.
    However, you can try thru open hub.
    Ravi Thothadri

  • How Can I use "textBee" Attribute of  xhtmlb:pager

    Hi everyone...
    I used "textBee" attribute like below...
    DATA: bee TYPE REF IF_BSP_BEE.
    DATA: html_bee TYPE REF TO CL_BSP_BEE_HTML.
    CREATE OBJECT html_bee.
      html_bee->add( html1 =
                                 html6 =  ).
    bee = html_bee.
                    <xhtmlb:pager id     = "pg1"
                                  text   = "Page [$vIndex$] of $vMax$"
                                  textBee   = "<%= bee %>"
                                  vMax   = "<%= lines( itab ) %>"
                                  design = "VERTICAL_SIMPLE+INDICATOR" />
    It does not work... How can I use this???

    Hi,
    Did you check things like
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bsp/htmlb&
    http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/3ff4ac67a5b14e8cd260d7b42f0f06/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/28/4bae407e69bc4ee10000000a1550b0/content.htm
    Eddy

  • Can I use Nav Attribute of a Nav Attribute for Drill Down....??

    Hello Gurur:
    I have a strange request.  We need to use 0EMPLOYEE in our Cube, whic has 'Comp. Code', 'Cost Center' 'User ID' as Nav Attributes.  "Com Pcode" has Nav attributes 'Global Divison" "Subsidiary" etc.
    We need to use the 'Global Division' ifor Selection in Dashboard and Web templates.  The only way to use it with 0EMPLOYEE" would be to use Variable on a Nav. Attribute of a Nav Attribute. ......  So involves 2 jumps.
    Is this something possible??  I have my doubts but has anyone seen done this?  Can someone please shed some light.
    Thanks a ton in advance,........
    Best  PBSW

    Hi pbsw2009:
       To answer your question, yes, that is possible, in fact that is what SAP calls "Transitive Attributes".
    In other words, Global Division is a Transitive Attribute of 0EMPLOYEE (in your scenario).
    Take a look at this document, "Understanding Transitive Attributes"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90efdd6e-c86e-2910-db9c-87da68b3fc57?quicklink=index&overridelayout=true
    Regards,
    Francisco Milán.
    Edited by: Francisco Milan on Apr 27, 2010 10:31 AM

  • Can autoreply use Mail attribute for From header in autoreply?

    Hi:
    We've recently moved from 5.x to 6.2, and users are complaining that autoreply/vacation messages are coming with the user's mailEquivalentAddress in the From: header rather than the email address that is in the Mail attribute. In our case, Mail is set to [email protected]
    Here's our version info:
    jeffw@ash:/ims/log# imsimta version
    Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
    libimta.so 6.2-3.04 (built 01:43:03, Jul 15 2005)
    SunOS ash.usg.tufts.edu 5.9 Generic_118558-08 sun4u sparc SUNW,Netra-T12

    Well, "noreverse" will prevent "from" address from being rewritten.
    However, from your description of the problem, it's likely to have no effect at all.
    A normal rewrite is when a "mailAlternateAddress" gets rewritten. You said you use "mailEquivalentAddress". That should never be rewritten. If you're indeed using "mailAlternateAddress", then it might work. Try it.... If you're really using, "mailEquivalentAddress", then Sanjay is barking up the wrong tree......

  • Data one hour off in VI Logger and can't use navigation bars

    I believe after Daylight savings time in October my data appeared one hour behind in the Historical Data view in VI Logger. This would not be so big of a problem, but when I go to use the navigation tools to skip through the data or zoom in and zoom out, they do not work and the screen is always taken back to the original time (where there is no data because it is one hour behind.) My data is sampled at 50,000 samples/sec for about 1 minute, so it takes forever to scroll through the data at this sampling rate.
    I tried re-setting the time in my Window's system, but this did not help.
    Please help!!!

    Hi,
    There is a KB regarding this issue:
    KB 330J3S0U: Why Do My VI Logger Timestamps Seem To Be Off By An Hour?
    I would actually recommend referring to the related link on the bottom referring to Citadel Handling Daylight Savings Time. To workaround the Daylight Savings Time, 2 queries are made -- one prior to Daylight Savings Time and one after. Then the two queries are merged to get the entire range of data.
    Hope this helps.
    Kileen

  • In which countries can I use navigation with Nokia...

    Navigation requires that there is navigable map for the country. Navigable maps are currently available for the countries below (with map data version 0.2.46.103 or 0.1.29.100, May 2012).
    (Note that if using Nokia Drive in Nokia Lumia phones, the initial Drive version in these phones doesn't yet support China even though there is navigable map for China.)
    Current navigable maps as at September 2011: 
    Andorra
    Angola (partial coverage)
    Argentina
    Aruba (partial coverage)
    Australia
    Austria
    Azerbaijan (partial coverage)
    Bahamas
    Bahrain
    Belgium
    Belize (partial coverage)
    Bermuda (partial coverage)
    Bolivia (partial coverage)
    Botswana
    Brazil
    Brunei
    Bulgaria
    Burundi (partial coverage)
    Canada
    Cayman Islands
    Chile
    China (incl. HK & Macau)
    Colombia
    Costa Rica (partial coverage)
    Croatia
    Cuba (partial coverage)
    Czech Republic
    Denmark
    Dom. Republic (partial coverage)
    Ecuador (partial coverage)
    Egypt
    El Salvador (partial coverage)
    Estonia
    Finland
    France (incl. French Guiana, Guadeloupe, Martinique & La Réunion)
    FYROM (Macedonia)
    Germany
    Ghana (partial coverage)'
    Great Britain
    Greece
    Guatemala (partial coverage)
    Guyana (partial coverage)
    Hungary
    Iceland
    India
    Indonesia
    Iran
    Iraq (partial coverage)
    Ireland
    Italy
    Ivory Coast (partial coverage)
    Jamaica (partial coverage)
    Jordan
    Kazakhstan
    Kenya
    Kuwait
    Latvia
    Lebanon
    Lesotho
    Liechtenstein
    Lithuania
    Luxembourg
    Libya (partial coverage)
    Malawi (partial coverage)
    Malaysia
    Maldives (partial coverage)
    Malta
    Mexico
    Monaco
    Montenegro (partial coverage)
    Morocco
    Mozambique
    Namibia
    Nepal (partial coverage)
    Netherlands
    New Zealand
    Nigeria
    Norway
    Oman
    Paraguay (partial coverage)
    Peru
    Philippines
    Poland
    Portugal (incl. Azores)
    Puerto Rico
    Qatar
    Romania
    Russia
    Rwanda (partial coverage)
    San Marino
    Saudi Arabia
    Singapore
    Slovakia
    Slovenia
    South Africa
    Spain
    Sri Lanka (partial coverage)
    Suriname (partial coverage)
    Swaziland
    Sweden
    Switzerland
    Taiwan
    Tanzania 
    Thailand
    Trinidad and Tobago (partial coverage)
    Turkey
    Uganda
    Ukraine
    United Arab Emirates
    Uruguay
    USA (incl. US Virgin Islands)
    Vatican
    Venezuela
    Vietnam
    Yemen (partial coverage)
    Zimbabwe (partial coverage)
    If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

    Nokia is working to include more countries in the Maps offering, but unfortunately we are not able to give timelines for any specific country.
    If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

  • Use of navigation attributes in APO DP

    I am trying to clarify how navigation attributes compare with full planning characteristics in APO DP (V5).
    In general, I know that navigation attributes are used for selection and navigation in APO DP.
    But suppose I have a navigation attribute called 'product type' for planning characteristic 'product'. Isn't it also possible to forecast and make adjustments at the 'product type' level.
    If the answer is yes, what is the real difference between the use of navigation attributes and planning characteristics?
    Thanks for any help with this.
    Bob Austin

    You do not see difference in Attribute and characteristics in the interactive planning screen. So you should be able to create selections and do general navigation
    just a little more detail on the difference between nav attributes and planning char
    But creating forecast profiles might be a problem- Selections with navigational attributes do not create forecast assignment table entries. As of SCM4.1, the attribute information can be stripped out of the selection via BADI, allowing an assignment entry to be created.
    Maintenance of CVCs also have to be done differently. Navigational attributes are not same as CVCs. Instead they point at the value of another characteristic. We create master data for nav attrib in the Admin workbench. Also If you plan to use navigational attributes on standard characteristics, say in 9AMATNR, then you could have issues in SNP since SNP does not support Nav attrib
    Also realignment of Navigational attributes is not a standard process but can be done.

Maybe you are looking for